Recovered and completed the follow-up request.
The client did what the clause requires.
What was measured
- Client
- quinn — quinn + h3 (our fork), noq fork
- Test
- 103 Early Hints before the final response —
h-early-hints - Clause
- RFC 9110 §15.2, RFC 8297 (MUST)
- Class
- resilience — Recovered rather than giving up.
- Required behaviour
- Treat 103 as informational and keep reading for the final response. RFC 9110 §15.2 makes this a MUST: a client "MUST be able to parse one or more 1xx responses received prior to a final response, even if the client does not expect one". Ignoring the hints is fine — a user agent MAY do that — but closing the connection is not.
- 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 quinn at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-early-hints"]'
What this suite is · The full grid · All clients · All tests · Findings