What this tests
parsingheaders
Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.
Anatomy
The response is `callback({...});` — your JSON arrived wearing a function call, because the endpoint's content negotiation decided you wanted JSONP, which is a technology from an era when the same- origin policy was considered more of a suggestion. Every JSON parser dies on the leading 'callback(' the way a dog dies on a fence. Found in the wild wherever a legacy API was "REST-ified" without removing the JSONP shim, which is most of the APIs built between 2008 and 2014 and a depressing number built since. The Content-Type will say application/javascript, helpfully confirming that what you received is code, not data, and must be executed by a browser or rejected by a parser — your parser chose neither, it just died. Correct behaviour: notice the callback wrapper, either strip it and parse the JSON within or refuse on the grounds that you are not a script-tag from 2011. Incorrect behaviour: eval() it. Please do not eval() it. This is a catalogue of failure, not a suggestion box.
Replay it
curl -i https://faultydata.com/r/FD-2026-052
// response appears hereSignature
{Status:200 Headers:map[Content-Type:application/javascript; charset=utf-8] Body:callback({"user":{"id":12345,"name":"ada"},"ok":true}); Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-036 — Content-Encoding lie (gzip header, plain body) FD-2026-039 — XML where JSON was promised FD-2026-058 — CSV when JSON was expected FD-2026-019 — JSON body, text/plain label FD-2026-041 — Retry-After as HTTP-date FD-2026-086 — charset=utf-16 lie on a UTF-8 body