Tests: HTTP/3 reserved frame type on a request stream - #96
Open
tahmid-23 wants to merge 1 commit into
Open
Conversation
Added tests for a reserved frame (RFC 9114, Section 7.2.8) sent on a request stream whose body is read: with a payload after the body, between two DATA frames, and with an empty payload. Without the corresponding fix, the first two are rejected as a prematurely closed stream and the second splices frame header bytes into the request body. A h3_frame() helper is added to send a frame of an arbitrary type.
tahmid-23
force-pushed
the
fix/h3-parse-skip-length
branch
from
August 26, 2026 20:09
df12499 to
cb4543e
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
2 participants
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.
Proposed changes
This provides regression tests against the bug presented in nginx/nginx#1624 by using reserved frames.
Checklist