Work to support Cache-Control, Content-Disposition, Content-Encoding, Content-MD5, x-amz-server-side-encryption-customer-algorithm, x-amz-server-side-encryption-customer-key, and x-amz-server-side-encryption-customer-key-MD5 started with #1258, but there are still some issues that prevent use of these headers.
Regarding header values of custom headers, I think the best approach is to simply leave these alone. If encoding is needed, the developer integrating with Fine Uploader S3 will need to properly encode these values before forwarding them on to Fine Uploader.
feat(s3): don't encode, prefix, or lower-case certain params
- unit tests
- doc updates
feat(s3): support for special params/headers - chunked requests
feat(s3): support for special params/headers - v4 chunked requests
test(s3): test support for special params/headers - v4 chunked requests
docs(s3): header documentation section
This has been completed and is available in the develop branch as 5.5.0-2. I plan to release this with 5.5.0.
What's the ballpark for the 5.5.0 release? Curious for my own migration planning purposes.
@neilchaudhuri I will be on a short vacation for most of this week, and I plan to release 5.5.0 mid-next week, perhaps around the 20th or 21st. If I run into issues during final testing, I'll aim for a release the following week, provided the issues encountered are not significant.
All tests are passing in all supported browsers, so the release of 5.5.0 next week is likely.
chore(build): inc build num