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
The Varnish cache's 503 page — "Error 503 Service Unavailable / Guru Meditation" — is one of the most-seen error documents in internet history, and the source of a thousand confused user tickets asking what meditation had to do with anything. It's a deliberate homage to the Amiga's crash screen, because the Varnish authors understood that if you're going to fail, fail with references. When you see it, your origin is down and the cache is standing in front of the wreckage doing its best impression of a website. From the client's side: a 503 with an X-Varnish ID, an HTML body aimed at humans, and not a scrap of JSON in sight — the cache layer's way of saying "the thing you want is behind me, and behind me is on fire". Clients that parse every error body as JSON will produce a syntax error pointing at HTML, which is accurate in the way that "the bridge is out" is accurate when you're already in the river.
Replay it
curl -i https://faultydata.com/r/FD-2026-047
// response appears hereSignature
{Status:503 Headers:map[Content-Type:text/html; charset=utf-8 X-Varnish:1847489127] Body:<!DOCTYPE html><html><body><h1>Error 503 Service Unavailable</h1><p>Service Unavailable</p><h3>Guru Meditation:</h3><p>XID: 1847489127</p><hr><p>Varnish cache server</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-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-013 — Wrong types in a valid envelope