# HTTP/2 headers across an out-of-order segment

Twelve cleartext HTTP/2 requests in small TCP segments, one segment out of order; later requests reuse HPACK table entries built by earlier ones.

- What success looks like: All twelve request paths decoded.
- What error it exposes: HPACK decoded in arrival order instead of stream order.
- Kind: synthetic (generated, no real traffic)
- Protocols: HTTP/2 (cleartext), HPACK, TCP
- Keys: none (cleartext)
- Expected decoded output: h2c-headers-out-of-order.expected.json (JSON), confirmed by an independent decoder before publication
- Regenerate: cargo run -p synthetic-pcap --example hpack_hole_gen -- --name h2c_hpack --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: h2c-headers-out-of-order.zip holds these files, the licence text (LICENCE.txt) and their SHA-256 (SHA256SUMS)

## Files

- h2c-headers-out-of-order.pcapng
- h2c-headers-out-of-order.expected.json
- h2c-headers-out-of-order.md