Add ability to set custom Content-Encoding header on a per file basis #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Like
metadataMap
,manualContentEncoding
allows you to set theContent-Encoding
header using some arbitrary logic in a function:This is useful for when S3's auto content encoding detection won't work for you (like when you need to support gzipped files on older browsers where the extension needs to be
.gz.js
and not.js.gz
).