PQ Crypta Logo

quic-go — Field line indexing a static table entry that does not exist

The client did something the clause forbids, or failed to do what it requires.

Jump to an anomaly59

Every one of these is a page: what the server emits, the clause it is judged against, and how each client answered. The full list carries the verdict tallies too.

Fail

rejected the field section with QPACK_DECOMPRESSION_FAILED, but as a stream error: it stopped the request stream and kept the connection open. The code is right and the scope is not -- RFC 9204 makes every decompression failure a connection error.

The client did something the clause forbids, or failed to do what it requires.

What was measured

Client
quic-go — quic-go, quic-go v0.65.0 (h1:RAro2j2yN9a9)
Test
Field line indexing a static table entry that does not exist — h-qpack-static-index-invalid
Clause
RFC 9204 §3.1, §4.5.2 (MUST)
Class
correctness — Rejected something invalid, with the code the RFC names.
Required behaviour
Close the connection with QPACK_DECOMPRESSION_FAILED (0x200). The static table has 99 entries, so index 200 refers to nothing, and §3.1 is explicit: "When the decoder encounters an invalid static table index in a field line representation, it MUST treat this as a connection error of type QPACK_DECOMPRESSION_FAILED." The static table needs no permission and never changes size, so unlike the dynamic-table tests this one applies to every client.
Measured
2026-11-22

Reproduce it

The suite is the judge, so the reproduction is to point the same client at the same test and let the server report what it saw.

SESSION=$(curl -sX POST https://conformance.pqcrypta.com/session | jq -r .id)
# then drive quic-go at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-qpack-static-index-invalid"]'

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions