What this tests
timeoutsparsing
Point your client at this specimen and find out — before prod does — whether it has a timeout, and whether the timeout has a timeout.
Anatomy
Content-Length says 2048. The body is 64 bytes. The server has already closed its side of the deal — or at least stopped talking — and your client is now waiting for 1984 bytes that were described, promised, and never produced. Like a removal van that arrives with one box, says "rest's coming", and drives off into a field. Delivered via raw socket write because honest HTTP stacks refuse to lie at the protocol level — this requires bypassing the entire civilized layer of the stack, which is also how it happens in production: a proxy truncates, a stream aborts, a backend crashes mid-write with the header already committed. Clients that read until Content-Length will hang until their read deadline fires — if they have one. Clients that read-until-close get a truncated document and must decide whether partial data is better than no data, which is a product decision disguised as a read loop.
Replay it
curl -i https://faultydata.com:8443/r/FD-2026-070
This exhibit breaks the connection itself, so replay it on the direct line (port 8443), where nothing sits between you and the bytes. On the main site the web server in front tidies the wreckage into a polite 502, and the button below will show you exactly that.
// response appears hereSignature
{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw:HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 2048
X-Fault-Specimen: FD-2026-070
{"truncated":true,"note":"the other 1984 bytes never arrived"} Phases:[]}
Keep digging
FD-2026-081 — Response dies mid-headers FD-2026-084 — Response body larger than expected (2MB JSON) FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-019 — JSON body, text/plain label FD-2026-041 — Retry-After as HTTP-date FD-2026-071 — 204 No Content... with content