Update: February 11, 2014 – 4.3.1 Hotfix Release
This hotfix release addresses the following issues:
- HTTP is now used as the default scheme for S3 endpoints rather than HTTPS (#1129)(Reverts: #1119)
- Apply display.fileSizeOnSubmit only to files submitted by the user (#1130)
Here are some notable additions that are part of the 4.3 release:
Upload Files Directly to Azure From Your Browser
In 3.8, we added the ability to upload directly to Amazon’s S3 service directly from your browser, in all supported browsers. Starting with 4.3, you will be able to send these files directly to Microsoft’s Windows Azure Blob Storage service as well. You can read more about this feature on our documentation site. We have even provided a C# example for signing the requests that Fine Uploader Azure makes.
Please note that uploads directly to Azure are not possible in Internet Explorer 9 and older. This is due to a shortcoming of Azure’s API.
Easily Connect Fine Uploader to an Existing HTML Form
Default S3 endpoint to HTTPS if no scheme indicated.Reverted in #1129
- Pass the ETag from S3’s response to a non-chunked upload request to the upload success endpoint.
- Allow optional S3 server-side encryption for all uploaded files.
- Ensure getButton method, when called in an onSubmit callback, returns the upload button associated with a file.
- Allow ACL to be specified on a per-file basis.
- S3 chunked uploads fail if parameter names include uppercase letters.
- Traditional endpoint uploads reported as successful if response body contains success:true, even if response status is not 200.
- Exception if multiple files are dropped when the multiple option is set to false.
As always, for up-to-date information about features and fixes planned for the next release (4.4), please see the milestone in the Github issue tracker. We will begin to plan the 4.4 release shortly after this release of 4.3.