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

The 302 is valid, the Location is valid, the destination is a 404. A redirect chain with a dead end — the signpost is perfect, it just points at a hole in the ground. This happens constantly in the wild wherever a service moved a resource and forgot the second hop, or a marketing redirect outlived the campaign it pointed at. Clients that follow redirects get a surprise: they asked for data, followed the chain correctly, and landed on a 404 they had no hand in creating. Whether the client attributes the 404 to the redirect or to itself determines how the incident report reads — "target not found" vs "the redirect led nowhere", which is the difference between debugging and archaeology. This specimen 302s to a path that does not exist, so the chain resolves to a genuine 404 — a real one this time, not an exhibit.

Replay it

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

// response appears here

Signature

{Status:302 Headers:map[Location:/r/FD-1999-001] Body:{"redirect":"/r/FD-1999-001","note":"the destination does not exist. that is the exhibit."} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-099 — Redirect loop 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