What this tests
headersretry-logic
Point your client at this specimen and find out — before prod does — whether it reads the headers, or just the status code.
Anatomy
X-RateLimit-Remaining proudly announces seven requests left. The status line disagrees: 429, right now, hard no. The headers were computed by a different bucket than the one doing the enforcing — edge counts one thing, origin counts another, and each writes its own version of the truth like two witnesses to the same bar fight describing different fights. Clients that trust the counter walk confidently into the wall — the header said seven, so the retry logic scheduled seven more, each one bounced, each one decrementing a remaining count that was fictional to begin with. It's the API equivalent of a petrol gauge calibrated by a different car. The correct response is to trust the status code over the headers — status is enforced, headers are advisory, like the difference between a law and a leaflet. Your client will either learn that here or during a real rate-limit incident. Both are educational. Only one is funny.
Replay it
curl -i https://faultydata.com/r/FD-2026-038
// response appears hereSignature
{Status:429 Headers:map[Retry-After:5 X-RateLimit-Limit:100 X-RateLimit-Remaining:7 X-RateLimit-Reset:1893456000] Body:{"error":"rate limited"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-041 — Retry-After as HTTP-date FD-2026-073 — Retry-After: 0 (storm bait) FD-2026-102 — Rate-limit headers that lie FD-2026-001 — Stripe-style rate limit FD-2026-019 — JSON body, text/plain label FD-2026-069 — Unsolicited 304 to an unconditional request