Add support for Zstandard content-type #381
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
dlindenkreuz
changed the title
|
Thanks for the PR, please add docs and test and this is ready to go! |
wojtekmach
reviewed
Jul 4, 2024
|
Done. In the meanwhile, MIME has been updated to 2.0.6, which adds support for Zstd. Req currently requires MIME |
wojtekmach
reviewed
Jul 4, 2024
|
Thank you! |
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.
Although Req has long supported Zstandard
content-encoding, it does not yet support Zstandardcontent-typewhich is used for original.zstarchive files (as opposed to encoding other original media types like JSON for transfer).This PR adds automatic decompression when
:ezstdis available andcontent-type: application/zstdis detected. It depends on an upstream change in the MIME package: elixir-plug/mime#82