PQ Crypta Logo

curl — 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

Objected at the QUIC layer (rejected at the QUIC layer with INTERNAL_ERROR) instead of signalling the HTTP/3 error. The violation was detected and rejected, which is the right instinct; §8.1 requires an HTTP/3 connection error to be carried in an application close, and this test names 0x200. A transport close carries no HTTP/3 code at all, so a peer has no way to learn what was wrong.

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

What was measured

Client
curl — ngtcp2 + nghttp3, libcurl/8.23.0 ngtcp2/1.26.0
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 curl 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