What this tests
semantics
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
RFC 5842's contribution to the status code menagerie: 508, for when the server detects an infinite loop inside WebDAV property traversal. Almost nothing emits it, almost nothing handles it, and clients that pattern-match "5xx = retry" will retry a request whose defining characteristic is that it can never terminate. A fine test of whether your error handling reads the status or just the first digit.
Replay it
curl -i https://faultydata.com/r/FD-2026-104
// response appears hereSignature
{Status:508 Headers:map[Content-Type:application/json] Body:{"error":"loop_detected","detail":"the resource graph contains a cycle, much like this incident review"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-004 — GitHub secondary rate limit FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-023 — Global 502s from a bad WAF rule (Cloudflare, Jul 2019) FD-2026-029 — Production database deleted, backups broken (GitLab, Jan 2017) FD-2026-030 — Dependency vanishes from the registry (left-pad, Mar 2016) FD-2026-047 — Guru Meditation (Varnish cache failure)