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
A Cloudflare 522: the edge made it to your origin, knocked politely, and got nothing — connection timed out at the doorstep. The user gets a branded HTML error page designed by a professional, for humans, with a little illustration. Your API client gets the same thing, because the edge does not know and cannot care that you're a robot. So: HTTP 522, Content-Type text/html, a body full of friendly troubleshooting advice aimed at a species that includes your PM but not your parser. The API contract — JSON in, JSON out, or at least a dignified status code — has been replaced by marketing collateral. Clients that check Content-Type survive. Clients that blindly json.Parse get a syntax error pointing at HTML, and someone will spend an hour convinced your API "returned invalid JSON", which is technically true in the way a fire is technically warm.
Replay it
curl -i https://faultydata.com/r/FD-2026-010
// response appears hereSignature
{Status:522 Headers:map[Content-Type:text/html Server:cloudflare] Body:<!DOCTYPE html><html><body><h1>Error 522</h1><p>Connection timed out</p></body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-066 — Captive portal interception (HTTP 511) FD-2026-067 — Legally unavailable (HTTP 451, geo-block) FD-2026-068 — Batch partial success (HTTP 207 Multi-Status) FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-035 — Stack trace in the error body FD-2026-047 — Guru Meditation (Varnish cache failure)