Ray Nicholus

The only way to accomplish this without a breaking change would be to allow headers to be specified explicitly for the signature request.

Any changes to the body of the request will be breaking changes, so that can't happen until the next major version release. Currently, the payload of the signature request for...

Most likely, I will opt to add an API method to specify headers for the signature request, and then you can send the token in a header. I _really_ don't...

Changes to Fine Uploader internal code yes, but I don't see these being breaking changes. A new API method would have to be added to allow users to specify headers...

This is not a bug, rather it is intentionally in place to work around bugs in video file uploading present in current iOS Chrome and previous versions of iOS Safari....

It's possible though that this should only be in place for Chrome. I'll keep this open so I remember to ensure this isn't affecting any version of safari newer than...

If you set [the `workarounds.ios8EmptyVideos` option](http://docs.fineuploader.com/branch/master/api/options.html#workarounds.iosEmptyVideos) to `false`, it should allow the `multiple` attribute to be added to the file input in iOS.

In Fine Uploader 6.0, I plan on removing this workaround, even though iOS Chrome may still have this issue. Along with removing the workaround, we'll probably pull support for iOS...

TODO here for 6.0: - [x] Remove `workarounds.ios8EmptyVideos` option - [x] Remove support for iOS Chrome - [x] Remove `workarounds.ios8BrowserCrash`option. This should not be an issue anymore. - [x] Remove...

No problem. That's one of the (many) things that makes Fine Uploader a better choice than any of the other upload libraries.