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
One request, two responses back-to-back on the socket — the second one smuggled behind the first like a fake ID tucked inside a real wallet. HTTP response splitting: user input containing CRLF ends up in a header, the response gets cut in two, and the client — which asked for one response — gets two and must decide which gospel to believe. This is an actual attack primitive, not just a parsing quirk: poison the second response, and a downstream cache stores your version under someone else's URL. The polite version, replayed here, is two well-formed responses for the price of one — a 200 and a 500 sharing a connection. Clients that read one response and close are safe. Clients that pipeline or reuse connections will encounter the smuggled response as the answer to their NEXT request, which is where the fun — legally distinct from the good kind — begins.
Replay it
curl -i https://faultydata.com:8443/r/FD-2026-082
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: 28
X-Fault-Specimen: FD-2026-082
{"ok":true,"which":"first"}HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 34
{"ok":false,"which":"smuggled"} Phases:[]}
Keep digging
FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-071 — 204 No Content... with content FD-2026-080 — HTTP/0.9-style response (body, no status line) 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)