adds other compression types of encoding #496
Closed
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
adamchainz
requested changes
May 16, 2024
There was a problem hiding this comment.
Perhaps we should send in binary if any Content-Encoding header is set? It seems this list covers all values except compress: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding
Also, please add a changelog entry and update tests.
|
Superceded by #526. |
adamchainz
added a commit
that referenced
this pull request
Oct 7, 2024
Fixes the issue reported in #496.
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.
The dash app we used apig-wsgi to deploy to lambda had flask_compress enabled in the app which was using br encoding which wasn't being caught in the _should_send_binary.