Parse buffered HTTP framing before EOF - #187
Open
kentbull wants to merge 1 commit into
Open
Conversation
Attempt to consume complete request and response framing already present in the parser buffer before treating EOF as premature closure. Reject partial status lines, header blocks, and fixed-length response bodies at EOF so a parser cannot remain suspended after the connection has closed. Cover the framing boundaries with real Requestant, Respondent, and transport objects.
This was referenced Aug 29, 2026
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.
Summary
This adapts GLEIF-IT#22 to current upstream
main.Closes #186