https://bz.apache.org/bugzilla/show_bug.cgi?id=65343

--- Comment #1 from abernal <[email protected]> ---
Investigated this with a real server, sending a raw HEADERS frame (crafted by
hand, bypassing client-side validation) with no :authority and no Host header,
over h2c prior-knowledge.

Confirmed: this is not an httpd bug. nghttp2 (the underlying HTTP/2
implementation) rejects the frame in its own internal validation before httpd's
request-handling code ever sees it. The debug log shows:

  recv invalid FRAME[HEADERS[length=3, hend=1, stream=1, eos=1]]
  ...sent FRAME[RST_STREAM[...error=1]]
  closing with err=1 protocol error

So the server does respond at the HTTP/2 protocol level -- it resets the stream
with PROTOCOL_ERROR -- it just never produces an HTTP-level status response (no
:status header), since nghttp2 itself refuses to hand the malformed request up
to httpd. That matches "no response" if the tool used (h2i) only looks for a
HEADERS response and doesn't surface the RST_STREAM. This is consistent with
(and arguably required by) RFC 9113's pseudo-header validation happening at the
HTTP/2 framing layer, not something httpd's own code controls.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to