Skip to content
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

QPACK decoder should fail connection if the encoder blocks more than SETTINGS_QPACK_BLOCKED_STREAMS #7635

Closed
lachlan-roberts opened this issue Feb 22, 2022 · 0 comments · Fixed by #7660
Assignees
Labels
Bug For general bugs on Jetty side http3

Comments

@lachlan-roberts
Copy link
Contributor

Our QpackEncoder will not block more than SETTINGS_QPACK_BLOCKED_STREAMS streams.
But the QpackDecoder also needs to perform verification of this and fail the connection if this is violated.

https://datatracker.ietf.org/doc/html/draft-ietf-quic-qpack-21#section-2.1.2

If a decoder encounters more blocked streams than it promised
   to support, it MUST treat this as a connection error of type
   QPACK_DECOMPRESSION_FAILED.
@lachlan-roberts lachlan-roberts added the Bug For general bugs on Jetty side label Feb 22, 2022
@lachlan-roberts lachlan-roberts self-assigned this Feb 22, 2022
lachlan-roberts added a commit that referenced this issue Feb 28, 2022
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Feb 28, 2022
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue May 13, 2022
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue May 16, 2022
…axBlockedStreams

Issue #7635 - implement maxBlockedStreams logic in QpackDecoder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side http3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant