What this tests

headersparsing

Point your client at this specimen and find out — before prod does — whether it reads the headers, or just the status code.

Anatomy

Perfectly good JSON wearing a text/plain badge — some middleware rewrote the header and nobody audited it, because who checks? The bytes are fine. The label is a lie. It's a filing cabinet marked "invoices" that turns out to contain a perfectly organized collection of... invoices. The problem is entirely bureaucratic. And yet it separates the flock cleanly. The pedants sniff the content, spot the JSON, and parse anyway — technically wrong, practically right, like jaywalking to a fire escape. The literalists refuse on principle and log an error that will confuse an on-call engineer at 3am who will curl the endpoint, see perfectly valid JSON, and begin to doubt their own eyes. The data team, meanwhile, wonders why the "broken" feed works fine in curl. It always works fine in curl. That's the entire problem with curl.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:text/plain; charset=utf-8] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-041 — Retry-After as HTTP-date FD-2026-086 — charset=utf-16 lie on a UTF-8 body FD-2026-100 — Conflicting duplicate Content-Length headers FD-2026-036 — Content-Encoding lie (gzip header, plain body) FD-2026-039 — XML where JSON was promised FD-2026-052 — JSONP callback wrapper