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
HTTP 451 — "Unavailable For Legal Reasons", named after the temperature at which paper burns because the RFC authors had a sense of occasion — is the status a server returns when it cannot serve you for regulatory reasons. Most famously: half the American internet simply geo-blocking European visitors after GDPR rather than comply, which remains the most passive-aggressive response to legislation in computing history. For a client this is a 4xx that isn't your fault and isn't retryable — a "no" rooted in jurisdiction rather than anything you sent. Clients that retry it are tilting at legislation. Clients that treat all 4xx as "my request was bad" misdiagnose it. The correct response is to log it, geo-check yourself, and move on. This specimen serves a 451 with a compliance-shaped HTML body. Your client is not blocked; it is legally excluded, which sounds worse and behaves the same.
Source: RFC 7725 — An HTTP Status Code to Report Legal Obstacles · 2015-12-18
Replay it
curl -i https://faultydata.com/r/FD-2026-067
// response appears hereSignature
{Status:451 Headers:map[Content-Type:text/html; charset=utf-8 Link:<https://faultydata.com/legal>; rel="blocked-by"] Body:<html><body><h1>451 Unavailable For Legal Reasons</h1><p>This content is not available in your jurisdiction.</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-066 — Captive portal interception (HTTP 511) 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)