PQ Crypta Logo

A second GOAWAY naming a larger identifier than the first

Close the connection with H3_ID_ERROR. §5.2 permits multiple GOAWAY frames but requires the identifier in each to be no greater than any previously sent, because the identifier is a promise about what will still be processed and raising it takes that promise back. "Receiving a GOAWAY containing a larger identifier than previously received MUST be treated as a connection error of type H3_ID_ERROR."

PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

h-goaway-increasing · RFC 9114 §5.2 · correctness · layer http3 · udp/4503 · MUST

Passing this means: Rejected something invalid, with the code the RFC names.

Anomaly type: control_stream

How each client answered

ClientVersionVerdictWhat 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 Pass Rejected with the required error code 0x108.
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 Pass Rejected with the required error code 0x108.
quic-go quic-go v0.61.0 Pass Rejected with the required error code 0x108.
quiche 0.30.0 Pass Rejected with the required error code 0x108.
neqo 0.31.1 Fail Rejected, but with error 0x101 where the specification requires 0x108. The violation was detected; the code reported is wrong.

What the clause requires

Close the connection with H3_ID_ERROR. §5.2 permits multiple GOAWAY frames but requires the identifier in each to be no greater than any previously sent, because the identifier is a promise about what will still be processed and raising it takes that promise back. "Receiving a GOAWAY containing a larger identifier than previously received MUST be treated as a connection error of type H3_ID_ERROR."

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-goaway-increasing")'

What this suite is · The full grid · All clients · All tests · Findings