Closed ggreenway closed 3 days ago
This is incorrect and inconsistent with the standard: https://datatracker.ietf.org/doc/html/rfc9113#name-request-pseudo-header-field
@danzh2010 @RyanTheOptimist for more comments
Some discussion on slack: https://envoyproxy.slack.com/archives/C9UGU858E/p1721771729606489
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
Not stale; there is a forthcoming QUICHE change to address this
QUICHE change with fix: https://github.com/google/quiche/commit/c8f5996fc2b0b2bf1f1a59fa5276e51884e3d458
FYI, that QUICHE change is now in envoy as of #35951.
Thanks!
QUIC streams with
Host
request header are rejected as invalid[2024-07-24 15:31:45.998][12][error][quic] [com_github_google_quiche/quiche/quic/core/http/quic_spdy_stream.cc:1789] host header is not allowed
Envoy allows (but discards) the
Host
request header for http/2 (see #30005). This should be consistent between h2 and h3.The failure happens in quiche, which has a hard-coded list of invalid headers checked in ValidateReceivedHeaders. The list of invalid headers is here.
Test case that currently fails and results in the above log message: