Repository navigation
Decompress HTTP/1.1 responses regardless of who set Accept-Encoding - #40
Merged
bogdanfinn merged 1 commit intoOct 27, 2026
Merged
Conversation
HTTP/1.1 now decodes based on the response's actual Content-Encoding whenever DisableCompression is false, matching the HTTP/2 path, instead of only when "gzip" appears in Accept-Encoding (addedGzip). (The original patch also made DecompressBody strip Content-Encoding and Content-Length on all paths and leave identity responses untouched; upstream's DecompressBody now does both.)
nicorobinreal
force-pushed
the
decode-h1-by-content-encoding
branch
from
October 27, 2026 00:47
380f09b to
dde370b
Compare
This file contains hidden or 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.
HTTP/2 already decodes responses by their Content-Encoding, but HTTP/1.1 only does when Accept-Encoding contains gzip, so a request asking for br or zstd comes back decoded over HTTP/2 and still compressed over HTTP/1.1; this makes HTTP/1.1 behave the same way (and updates the tests that expected the old behavior).