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
Your JSON API request wanders past the WAF on a Tuesday afternoon and gets bounced — not rejected, not 403'd, but handed a branded HTML challenge page. A JavaScript puzzle, an interstitial, a cheerful little "checking your browser" screen, delivered with HTTP 200 and Content-Type: text/html. Technically a successful response. Spiritually a hostage video. The client asked for application/json and received a CAPTCHA's overachieving cousin. Every parser downstream now has a choice: die loudly on the leading '<', or silently treat an anti-bot page as your data model — the two canonical ways to ruin an afternoon, available in one convenient specimen. This is what your monitoring sees: 200 OK, content delivered, green tick. What your pipeline sees: an HTML page where the invoice data used to live, like arriving at a library to find it has been replaced by a quiz.
Replay it
curl -i https://faultydata.com/r/FD-2026-008
// response appears hereSignature
{Status:403 Headers:map[CF-Mitigated:challenge Content-Type:text/html; charset=UTF-8] Body:<!DOCTYPE html><html><head><title>Just a moment...</title></head><body><h1>Checking your browser</h1><p>Enable JavaScript and cookies to continue</p></body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-035 — Stack trace in the error body FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) 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)