Content encoding #604
Closed
Content encoding #604
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
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.
This enables the content-encoding header on all uploaded artifacts to S3. This will not compress the file at rest, but rather on transfer to the client from S3. This will save on bandwidth costs.
See the section on content-encoding in the Digital Ocean docs for more information.
Most clients will automatically switch to using the compressed data such as web-browsers, but I am unsure about curl. It seems like you'd need to use the
--compressedflag to tell curl to uncompress the data.For some reason with the Chrome browser I got a "network error" when
compresswas not in the encodings list so I just added all of them for safety.