Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
The client did what the clause requires.
What was measured
- Client
- quic-go — quic-go, quic-go v0.61.0
- Test
- Response stream reset mid-body with H3_REQUEST_CANCELLED —
h-response-stream-reset - Clause
- RFC 9114 §8, §4.1 (MAY)
- Class
- discretionary — The RFC permits either behaviour; the report says which was chosen.
- Required behaviour
- Abandon the partial response — §4.1 says a response cancelled after a partial delivery "SHOULD NOT be used". Whether the connection survives is the client's to choose: §8 lets an endpoint "treat a stream error as a connection error under certain circumstances", so keeping the connection and closing it are both conformant. Stalling is the one wrong answer.
- 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 quic-go at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-response-stream-reset"]'