What this tests
semanticsparsing
Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.
Anatomy
HTTP 204 means "there is no body". This response has a body. The spec is unambiguous; the implementation was not consulted. Data arrives that the protocol swears doesn't exist — Schrödinger's payload, present and absent, depending on which part of the response you believe. Delivered raw because any self-respecting framework strips the body on a 204 automatically — producing this fault requires going around the framework, which is also how it happens in production: a proxy, a hand-rolled response writer, a legacy CGI script that prints status lines like it's 1997 and nobody's told it. Clients that trust the status code discard the body — fine, unless the body was the error message. Clients that read the body anyway get data the status code said wasn't there, which is technically a bonus and practically a compliance incident.
Replay it
curl -i https://faultydata.com:8443/r/FD-2026-071
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 204 No Content
Content-Type: application/json
X-Fault-Specimen: FD-2026-071
{"error":"this body should not exist but does"} Phases:[]}
Keep digging
FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-080 — HTTP/0.9-style response (body, no status line) 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)