This repository was archived by the owner on May 8, 2026. It is now read-only.
Limit QUIC stream and field section sizes to protocol max - #356
Merged
Conversation
Updated the default maxFieldSectionSize in Http3ConnectionHandler to (2^62) - 1, aligning with QUIC variable-length integer limits defined in RFC 9000. Introduced MAX_PEER_STREAMS_PER_STREAM_TYPE in EmbeddedQuicChannel and enforced this maximum for peer allowed streams, ensuring compliance with QUIC stream identifier constraints. **Motivation** QUIC uses 62-bit variable-length integers, allowing values up to (2^62) - 1. The previous default did not fully reflect this limit. Additionally, peer stream limits are applied per stream direction and initiator, but the current stream type model arbitrarily uses or allows Long.MAX_VALUE. This required enforcing a corrected maximum per stream type. **Modification** Set maxFieldSectionSize default to (2^62) - 1. Introduced MAX_PEER_STREAMS_PER_STREAM_TYPE to ((1L << 62) - 1) / 2 Enforced the maximum when storing peer allowed stream counts. **Result** Aligns HTTP/3 settings and peer stream limits with RFC 9000 and prevents invalid stream allocations. This is a port of netty/netty#16117
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Updated the default maxFieldSectionSize in Http3ConnectionHandler to
(2^62) - 1, aligning with QUIC variable-length integer limits defined in
RFC 9000. Introduced MAX_PEER_STREAMS_PER_STREAM_TYPE in
EmbeddedQuicChannel and enforced this maximum for peer allowed streams,
ensuring compliance with QUIC stream identifier constraints.
Motivation
QUIC uses 62-bit variable-length integers, allowing values up to (2^62)
Additionally, peer stream limits are applied per stream direction and
initiator, but the current stream type model arbitrarily uses or allows
Long.MAX_VALUE. This required enforcing a corrected maximum per stream
type.
Modification
Set maxFieldSectionSize default to (2^62) - 1.
Introduced MAX_PEER_STREAMS_PER_STREAM_TYPE to ((1L << 62) - 1) / 2
Enforced the maximum when storing peer allowed stream counts.
Result
Aligns HTTP/3 settings and peer stream limits with RFC 9000 and prevents
invalid stream allocations.
This is a port of netty/netty#16117