ngtcp2 — MAX_PUSH_ID sent by the server

Pass

Rejected with the required error code 0x105.

The client did what the clause requires.

What was measured

Client

ngtcp2 — ngtcp2 + nghttp3 (direct), 3c23148

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-09-18

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 ngtcp2 at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-max-push-id"]'