What this tests

semanticsparsing

Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.

Anatomy

You're behind a captive portal — hotel wifi, airport lounge, the train — and your API request has been intercepted by a machine that wants you to accept terms, watch an advert, or pay eleven pounds for bandwidth measured in sadness. The RFC defines 511 Network Authentication Required for exactly this. The portal returns a login page with a status code that tells the truth for once. From the client's chair it looks like the API has been replaced by a hospitality brochure: status 511, Content-Type text/html, a body full of checkboxes and a Wi-Fi logo. Every JSON parser dies on it. Every monitoring system reports the API "down" when actually the API is fine and YOU are the one in a hotel. The correct client behaviour is recognizing it isn't talking to the API at all — a distinction that matters, because retrying an API that doesn't know you exist is the most futile retry in the catalogue, and the catalogue contains a redirect loop.

Source: RFC 6585 — Additional HTTP Status Codes (511)

Replay it

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

// response appears here

Signature

{Status:511 Headers:map[Content-Type:text/html; charset=utf-8] Body:<html><body><h1>Welcome to Hotel WiFi</h1><p>Please accept the terms to continue.</p><form><button>Connect</button></form></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-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)