Bound HTTP/1 body reads. - #56
Merged
Merged
Conversation
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.
Fixed-length and chunked bodies now return at most 64 KiB from each read, independently of the underlying stream implementation.
Chunked bodies retain the remaining transfer chunk length across reads, allowing upper layers to enforce total representation limits without first buffering an entire adversarial transfer chunk. Chunk terminators are now validated strictly, and truncated chunks close the read side before raising
EOFError.The declared HTTP transfer chunk size remains unrestricted because transfer chunk boundaries do not carry representation semantics.
Tests cover bounded fixed and chunked reads, invalid chunk terminators, and incremental truncation handling.