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

Status line says 200. Content-Type says application/json. Content-Length says nothing, because there isn't one — and there isn't a body either. Just a confident, fully-formed promise of a payload followed by the vast empty auditorium where the payload was supposed to be. This is the response your API gives when the handler fell off the end of its own logic — every branch returned early, nobody wrote anything, and net/http politely shipped the blank page. The client asks "did it work?" and the server answers "yes," which is technically true in the same way a shrug is technically an answer. Clients split three ways: the ones that json.Unmarshal the void and get a nil map they then dereference into the shadow realm, the ones that treat empty as an empty list and quietly delete the pagination loop's reason to live, and the rare enlightened few that check whether a response body exists before believing in it. Be the third kind.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:application/json] Body: Corrupt:empty Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-013 — Wrong types in a valid envelope FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern) FD-2026-035 — Stack trace in the error body FD-2026-053 — SSO login page instead of your API response FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) FD-2026-072 — Success response confirming the wrong values