PQ Crypta Logo

neqo — Field section larger than the client's advertised maximum

The client did what the clause requires.

PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

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.

Pass

Decoded it and completed the request.

The client did what the clause requires.

What was measured

Client
neqo — neqo (Firefox), 0.31.1
Test
Field section larger than the client's advertised maximumh-oversized-field-section
Clause
RFC 9114 §4.2.2 (MUST)
Class
interoperability — Correctly decoded something valid but demanding.
Required behaviour
Handle it as an error against that one request, not the whole connection.
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 neqo at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-oversized-field-section"]'