What this tests

parsingsemantics

Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.

Anatomy

The server answers the request with raw body bytes and no status line at all — no "HTTP/1.1 200", no headers, just content, like it's 1991 and nobody's invented metadata yet. HTTP/0.9 lived like this, and a surprising amount of embedded gear, ancient CGI, and hand-rolled socket servers still does. Your HTTP client will either classify it as HTTP/0.9 and serve the body (technically correct per spec, spiritually a security incident waiting to happen), reject it as malformed, or panic in a code path nobody's exercised since the library's first commit. Delivered raw because no modern framework will produce it — this requires bypassing the entire HTTP stack and writing to the socket by hand, which is also how it happens in the wild.

Replay it

curl -i https://faultydata.com:8443/r/FD-2026-080

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 here

Signature

{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw:{"result":"ok","note":"no status line was harmed in the making of this response"} Phases:[]}

Keep digging

FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-071 — 204 No Content... with content FD-2026-082 — Two responses, one connection (response splitting) FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-013 — Wrong types in a valid envelope FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern)