Repository navigation
Read a gzip body without length from a socket stream - #162
Merged
svenvc merged 2 commits intoSep 24, 2026
Merged
Conversation
A gzip-encoded entity with neither Content-Length nor chunked transfer encoding, i.e. one delimited by closing the connection, was inflated directly from the socket stream. InflateStream asks its source for its #position while refilling, which ZdcSocketStream and ZdcSecureSocketStream do not understand, so reading such a response failed with a MessageNotUnderstood. The source is now wrapped in a ZnLimitedReadStream in that case too, as it already was for a gzip body with a Content-Length. ZnUnpositionableReadStream stands in for a socket stream in the test. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Read a gzip body without length from a socket stream
Owner
|
Thank you |
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.
A gzip-encoded entity with neither Content-Length nor chunked transfer encoding, i.e. one delimited by closing the connection, was inflated directly from the socket stream. InflateStream asks its source for its #position while refilling, which ZdcSocketStream and ZdcSecureSocketStream do not understand, so reading such a response failed with a MessageNotUnderstood.
The source is now wrapped in a ZnLimitedReadStream in that case too, as it already was for a gzip body with a Content-Length. ZnUnpositionableReadStream stands in for a socket stream in the test.