What this tests
loopsretry-logic
Point your client at this specimen and find out — before prod does — whether it bounds loops, or loops unboundedly until the invoice arrives.
Anatomy
This endpoint, when asked where the resource is, confidently points at itself. Where is it? Here. And where is here? Also here. A redirect Möbius strip — the HTTP equivalent of a receptionist who keeps directing you to her own desk with increasing enthusiasm. Every HTTP client has a redirect limit precisely because someone, somewhere, shipped this into production and got paged about it. curl gives up at 50. Browsers tap out around 20 with a page that says "this page isn't redirecting properly", which is true in the way that a house fire is a heating issue. Your hand-rolled fetch wrapper, the one written by a junior data engineer during what can only be described as a corporate goat-herding retreat for the soul? Never. It will follow forever, burning a hole through both ends of the pipe and billing you for the privilege. The specimen: one Location header, pointing home, forever. Bring your own exit condition.
Replay it
curl -i https://faultydata.com/r/FD-2026-020
// response appears hereSignature
{Status:302 Headers:map[Location:/r/FD-2026-020] Body:{"redirect":"/r/FD-2026-020"} 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-099 — Redirect loop FD-2026-001 — Stripe-style rate limit FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-004 — GitHub secondary rate limit FD-2026-005 — Token expires mid-session (Entra ID pattern)