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 says 847 requests in the tank. The status line says 429. Both arrive in the same response, which is the API equivalent of being fired by someone who's still smiling. This happens in production when the rate-limiter sits in a different layer than the headers' author — the gateway counts one thing, the app reports another, and your client's "be polite, check remaining" logic learns that remaining was aspirational. Defence: trust the status code, treat the headers as weather reporting.

Replay it

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

// response appears here

Signature

{Status:429 Headers:map[Content-Type:application/json Retry-After:60 X-RateLimit-Limit:1000 X-RateLimit-Remaining:847 X-RateLimit-Reset:1893456000] Body:{"error":"rate_limit_exceeded","remaining":847} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-038 — Lying rate-limit headers FD-2026-041 — Retry-After as HTTP-date FD-2026-073 — Retry-After: 0 (storm bait) FD-2026-001 — Stripe-style rate limit FD-2026-019 — JSON body, text/plain label FD-2026-069 — Unsolicited 304 to an unconditional request