# HTTP/2 response sent while the upload is still going

An HTTP/2 server sends its complete response (a 413) while the client is still uploading, then resets the stream with NO_ERROR; the rest of the upload arrives after the reset.

The response here is a 413; the live Sea trials case, h2.lab.shorenet.co.uk/f/h2-early-response, answers 200 instead, with the same framing.

- What success looks like: The whole response, and every DATA frame of the upload, including those sent after the reset.
- What error it exposes: A parser that waits for the request to end before reading the response.
- Kind: synthetic (generated, no real traffic)
- Protocols: HTTP/2 (cleartext)
- Keys: none (cleartext)
- Expected decoded output: h2-early-response.expected.json (JSON), confirmed by an independent decoder before publication
- Regenerate: cargo run -p synthetic-pcap --example h2_sequence_gen -- --fixture test-fixtures/rfc-vectors/rfc9113-h2-sequences/early-response-rst-no-error.json --name h2_early_response --out <dir>
- Licence: Creative Commons Attribution 4.0 International (CC BY 4.0), for the released capture and expected-output files only. Attribution: Shorenet Ltd.
- Download all: h2-early-response.zip holds these files, the licence text (LICENCE.txt) and their SHA-256 (SHA256SUMS)

## Files

- h2-early-response.pcapng
- h2-early-response.expected.json
- h2-early-response.md