PQ Crypta Logo

chromium — PUSH_PROMISE for a push the client never allowed

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

PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

Fail

Rejected, but with error 0x106 where the specification requires 0x108. The violation was detected; the code reported is wrong.

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

What was measured

Client
chromium — Chromium QUICHE, build 1223
Test
PUSH_PROMISE for a push the client never allowedh-push-promise-unsolicited
Clause
RFC 9114 §7.2.5, §4.6 (MUST)
Class
correctness — Rejected something invalid, with the code the RFC names.
Required behaviour
Close the connection with H3_ID_ERROR. §7.2.7 leaves the maximum push ID unset until the client sends MAX_PUSH_ID, so a server "cannot push until it receives a MAX_PUSH_ID frame" and every push ID is larger than the client has advertised. §7.2.5 is explicit about the answer: a client "MUST treat receipt of a PUSH_PROMISE frame that contains a larger push ID than the client has advertised as a connection error of H3_ID_ERROR".
Measured
2026-09-17

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

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