Note, for Amazon S3 support (or other APIs which expect just streaming the file), you may need an option for disabling multipart form encoding.
See this parallel effort in `angular-file-upload` (Angular1) https://github.com/nervgh/angular-file-upload/pull/602
and the related S3 corruption issue that it solves: https://github.com/nervgh/angular-file-upload/issues/382
Note: #224 should allow you to upload to Amazon S3 using pre-signed URLs. It's essentially the same fix that was applied to angular-file-upload (for Angular 1) as noted above.
Note: #224 should allow you to upload to Amazon S3 using [pre-signed URLs](http://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html). It's essentially the same fix that was applied to `angular-file-upload` (for Angular 1) as noted above.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Wondering if this is in the roadmap....
hm
Note, for Amazon S3 support (or other APIs which expect just streaming the file), you may need an option for disabling multipart form encoding.
See this parallel effort in
angular-file-upload(Angular1) https://github.com/nervgh/angular-file-upload/pull/602and the related S3 corruption issue that it solves: https://github.com/nervgh/angular-file-upload/issues/382
Note: #224 should allow you to upload to Amazon S3 using pre-signed URLs. It's essentially the same fix that was applied to
angular-file-upload(for Angular 1) as noted above.