PQ Crypta Logo

picoquic — MAX_PUSH_ID sent by the server

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

Accepted a protocol violation and carried on. The anomaly was on the control stream, and this client extended flow-control credit on it -- a receiver extends credit on a stream only once its application has consumed what was already there, so the bytes were read rather than merely delivered. This should have been rejected.

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

What was measured

Client
picoquic — picoquic + picotls, 3a0c3bc
Test
MAX_PUSH_ID sent by the server — h-max-push-id
Clause
RFC 9114 §7.2.7 (MUST NOT)
Class
correctness — Rejected something invalid, with the code the RFC names.
Required behaviour
Reject with H3_FRAME_UNEXPECTED. MAX_PUSH_ID travels client to server only, so a server sending one is using a frame in a direction the specification does not allow.
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 picoquic at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-max-push-id"]'

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions