Verify servers handle headers case-insensitive#1050
Open
Kaliumhexacyanoferrat wants to merge 1 commit into
Open
Verify servers handle headers case-insensitive#1050Kaliumhexacyanoferrat wants to merge 1 commit into
Kaliumhexacyanoferrat wants to merge 1 commit into
Conversation
Kaliumhexacyanoferrat
marked this pull request as ready for review
July 25, 2026 15:15
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
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.
Per RFC 9110 header names in H1 are supposed to be interpreted independent from their casing (so
content-lengthorCONTENT-LENGTHare both valid). As this requires the server to normalize the names before comparing them, this is somewhat performance relevant, at least in pipelining and maybe even on baseline - therefore we should verify that.