remove header field validation to comply with RFC.#1
Merged
vshakitskiy merged 5 commits intoMar 23, 2026
Conversation
Section 1.3: "Both the name and value are treated as opaque sequences of octets."
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.
Section 1.3 in the RFC:
"Both the name and value are treated as opaque sequences of octets."
This makes it much easier for HTTP/2 implementations to properly handle improper header names as stream errors separate from more fatal errors due to HPACK state mismatches.
The HPACK RFC also does not mention anything about validating header names or values.
This also has the added positive that the only Erlang FFI is removed, making the library pure gleam!