Recovered and completed the follow-up request. The client process had already exited 4410ms in, before this test's reaction point at never observed, so the silence after that is not evidence either way.
The client did what the clause requires.
What was measured
- Client
- quico — quico + lemon-tls, 0.7.0 (npm)
- Test
- GOAWAY sent mid-connection —
h-goaway - Clause
- RFC 9114 §5.2 (SHOULD)
- Class
- resilience — Recovered rather than giving up.
- Required behaviour
- Stop opening requests, finish those in flight, and retry idempotent ones elsewhere. The GOAWAY is written once the client's request is running and names the stream after it, so §5.2 puts that request inside the range the server promises to process: finishing it is the behaviour under test. Sent before the request instead, the correct answer would be to close and reconnect, and the test would be measuring a race rather than recovery.
- Measured
- 2026-10-15
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 quico at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-goaway"]'