Conversation
Decompress only acted on an exact "gzip" Content-Encoding, so a body sent with "GZIP" or "Gzip" reached the handler still compressed. Content codings are case-insensitive (RFC 9110 section 8.4.1). Backport of labstack#3056.
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
1 participant
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.
Backport of #3056 to v4.
Decompress only handled an exact
Content-Encoding: gzip. If a client sentGZIPorGzip, the body reached the handler still compressed. Content codings are case-insensitive (RFC 9110 §8.4.1), so the check now usesstrings.EqualFold.Added
TestDecompressContentEncodingCaseInsensitive. It fails before the change and passes after.go test ./...passes.