Support for ContentEncoding #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @dvonlehman Thank you for your contribution! A nice extra feature. Merged |
|
Would you like me to create a new release? |
|
A new release to npm would be great. Thanks. |
|
Released a new version. Sorry for the delay; it completely slipped my mind. Version is now: 0.0.5 Thanks for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi, I need the ability to store gzip encoded files in S3rver. The real S3 handles this with the ContentEncoding parameter on the putObject command. The PR includes code to read/write a contentEncoding key in the metadata file. Also I moved the functionality to create the test buckets into the mocha before block so it's possible to run one test at a time and have the test buckets exist. Added a new unit test for storing and reading a gzipped copy of jquery. All tests are passing when running
npm test.