feat: set Content-Type header to application/gzip|zstd when the compression property in the request was set #679
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
fengelniederhammer
force-pushed
the
665-fix-compression-headers
branch
from
87a1f0f
to
ca324fa
Compare
JonasKellerer
approved these changes
Feb 29, 2024
…ession property in the request was set #665 That way we lose information about the actual content of the request, but Chrome downloads zstd encoded data instead of failing to display it.
fengelniederhammer
force-pushed
the
665-fix-compression-headers
branch
from
d19998f
to
c06cf8c
Compare
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.
resolves #665
PR Checklist
[ ] All necessary documentation has been adapted.