HPACK decode failures must be treated as connection errors (COMPRESSION_ERROR)#625
Merged
arturobernalg merged 1 commit intoapache:masterfrom Feb 18, 2026
Merged
Conversation
…ON_ERROR) RFC 7540 / RFC 9113 require any HPACK decoding error to be handled as a connection error of type COMPRESSION_ERROR. Map HPACK decode failures (including decoder runtime failures) to H2ConnectionException and avoid stream-local handling. Add regression tests for HEADERS / PUSH_PROMISE.
ok2c
approved these changes
Feb 18, 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
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.
RFC 9113 4.3: “A decoding error in a field block MUST be treated as a connection error … of type COMPRESSION_ERROR.”
RFC 7540 4.3: “A decoding error in a header block MUST be treated as a connection error … of type COMPRESSION_ERROR.”