h-settings-on-request-stream
· RFC 9114 §7.2.4 · correctness · layer http3 · udp/4490 · MUST
Passing this means: Rejected something invalid, with the code the RFC names.
Anomaly type: response_stream
How each client answered
| Client | Version | Verdict | What happened |
|---|---|---|---|
| curl | ngtcp2/1.11.0 | Inconclusive | Objected, but at the QUIC layer (rejected at the QUIC layer with INTERNAL_ERROR), so the HTTP/3 error code could not be read. §8.1 carries an HTTP/3 connection error in an application close, and this test asks for 0x105 specifically — whether that was the client's reasoning is not observable from here. |
| quinn | noq fork | Inconclusive | The client completed its request and then said nothing further before the window closed. A rejection whose CONNECTION_CLOSE was lost cannot be told apart from a client that never objected: QUIC re-sends that frame only in answer to an incoming packet, so one that goes missing is simply never seen. |
| aioquic | 1.3.0 | Pass | Rejected with the required error code 0x105. |
| chromium | build 1223 | Pass | Rejected with the required error code 0x105. |
| quic-go | quic-go v0.61.0 | Pass | Rejected with the required error code 0x105. |
| quiche | 0.30.0 | Pass | Rejected with the required error code 0x105. |
| neqo | 0.31.1 | Pass | Rejected with the required error code 0x105. |
What the clause requires
Close the connection with H3_FRAME_UNEXPECTED. SETTINGS belongs to the control stream alone: §7.2.4 says that if an endpoint receives one on a different stream it "MUST respond with a connection error of type H3_FRAME_UNEXPECTED".
Judged against RFC 9114.
Run this one yourself
Every test is reachable from your own client. Nothing here needs an account.
curl -s https://conformance.pqcrypta.com/catalog.json \
| jq '.tests[] | select(.id == "h-settings-on-request-stream")'What this suite is · The full grid · All clients · All tests · Findings