What this tests

loopssemantics

Point your client at this specimen and find out — before prod does — whether it bounds loops, or loops unboundedly until the invoice arrives.

Anatomy

A 302 whose Location points back to the same URL. Every HTTP stack has a redirect limit — RFC 7231 suggests five-ish — and this specimen exists to find yours. Clients without limits discover a novel way to hold a connection open forever while accomplishing nothing, which is also a fair description of most meetings. Real-world provenance: every framework upgrade that ever shipped a trailing-slash handler fighting a canonical-URL middleware. Two well-meaning redirects, one infinite conversation.

Replay it

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

// response appears here

Signature

{Status:302 Headers:map[Location:/r/FD-2026-099] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-085 — Redirect chain that ends in a 404 FD-2026-020 — Infinite redirect loop FD-2026-004 — GitHub secondary rate limit FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-013 — Wrong types in a valid envelope