Repository navigation
fix(net): backport legacy request parameter decoding #5224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
d724a95
chore: claim request parameters backport
kixelated 7d2385e
fix(net): decode legacy request parameters by draft on release
kixelated 17b756b
style(net): format legacy FORWARD regression
kixelated c9d53ee
Merge release before request parameter iteration
kixelated a59a4d1
fix(net): recognize legacy request parameters before parsing
kixelated 6543012
Merge remote-tracking branch 'origin/release' into pr5224
kixelated e003464
fix(net): ignore repeated unrecognized legacy request parameters in JS
kixelated 7807264
fix(net): recognize legacy request parameters by their draft
kixelated File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When draft 15 is negotiated, parameter
0x30reaches this branch becausemessageParamKind()has no DYNAMIC_GROUPS entry, so PUBLISH and SUBSCRIBE_OK silently skip it as unknown and allow duplicate or out-of-range values. Draft 15 §9.2.1.11 defines this parameter on those messages and makes values above 1 a protocol violation. The Rust PUBLISH and SUBSCRIBE_OK decoders omit0x30as well, so add draft-specific recognition and validation in both implementations.AGENTS.md reference: rs/moq-net/AGENTS.md:L5-L5
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of scope for this backport. Neither
mainnorreleaseimplements DYNAMIC_GROUPS (0x30) in either language; this PR only bringsreleasetomain's legacy recognition. Before it, Rust refused any draft-15 PUBLISH or SUBSCRIBE_OK carrying 0x30, and JS stored it without validating the value. Skipping it is no less strict than JS was, and stops Rust closing the session over it. Validating DYNAMIC_GROUPS belongs onmainfirst, then a backport, so I'm proposing it as a follow-up rather than adding release-only behavior here.(Written by Claude Opus 5.5)