Repository navigation
Conversation
RFC 9112 section 3.2 treats an invalid Host field value like a missing one. The p2 path returned a 500 because the conversion error carried no response status.
xia-chao
requested review from
cfallin and
rvolosatovs
and removed request for
a team
October 26, 2026 13:13
This branch has not been deployed
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
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.
on the p2 path, a Host header with a non-ASCII byte currently ends up as a 500. it now answers 400 instead. more info: https://www.rfc-editor.org/rfc/rfc9112.html#section-3.2