h-push-stream-unpromised
· RFC 9114 §6.2.2 · correctness · layer http3 · udp/4504 · MUST
Passing this means: Rejected something invalid, with the code the RFC names.
Anomaly type: control_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 0x108 specifically — whether that was the client's reasoning is not observable from here. |
| quinn | noq fork | Inconclusive | The client completed its request and closed without objecting, but the anomaly was written to the control stream — a unidirectional stream nothing obliges it to read on any schedule. A one-shot request can finish before that stream is picked up, so this is equally consistent with accepting the violation and with never having seen it, and neither can be told from here. |
| aioquic | 1.3.0 | Inconclusive | The client completed its request and closed without objecting, but the anomaly was written to the control stream — a unidirectional stream nothing obliges it to read on any schedule. A one-shot request can finish before that stream is picked up, so this is equally consistent with accepting the violation and with never having seen it, and neither can be told from here. |
| chromium | build 1223 | Fail | Rejected, but with error 0x101 where the specification requires 0x108. The violation was detected; the code reported is wrong. |
| quic-go | quic-go v0.61.0 | Pass | Rejected with the required error code 0x108. |
| quiche | 0.30.0 | Fail | Rejected, but with error 0x103 where the specification requires 0x108. The violation was detected; the code reported is wrong. |
| neqo | 0.31.1 | Pass | Rejected with the required error code 0x108. |
What the clause requires
Close the connection with H3_ID_ERROR. §6.2.2 does not require the push to have been promised first — the stream alone is enough: a client "MUST treat receipt of a push stream as a connection error of type H3_ID_ERROR when no MAX_PUSH_ID frame has been sent", and no client under test sends one. Distinct from the PUSH_PROMISE test, which puts the same violation in a frame on the control stream. This one opens the push stream itself, which a client has to recognise by its stream type before any frame inside it is read.
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-push-stream-unpromised")'What this suite is · The full grid · All clients · All tests · Findings