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

You sent Accept: application/json. The API responded application/xml — the content negotiation silently fell through to a legacy serializer nobody has maintained since 2011, because the modern path is tested and the legacy path is load-bearing. Every parser dies on the leading '<', which is the HTTP equivalent of being handed a phone book when you asked for the time. Found wherever an old SOAP service is still wearing a REST trench coat: enterprise systems, banking integrations, anywhere the migration was "mostly done" and the last 5% was someone's job who has since left the industry entirely. The specimen exists to test your Accept-header handling and your parser's ability to say "that's not what I asked for" instead of attempting to XML-parse a response your entire worldview insists should be JSON. Dignity in refusal is a client virtue.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:application/xml] Body:<?xml version="1.0"?><response><user><id>12345</id><name>ada</name></user></response> 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-052 — JSONP callback wrapper 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