What this tests
headersretry-logicparsing
Point your client at this specimen and find out — before prod does — whether it reads the headers, or just the status code.
Anatomy
RFC 7231 permits Retry-After as delta-seconds OR an HTTP-date. Most backoff logic does int() on it and explodes the first time an API returns an actual date — like this one, which is implausibly far in the future because if you're going to test a parser you may as well test it with a date from a different decade. "Sun, 01 Jan 2034" is legal. Perfectly valid. Your int("Sun, 01 Jan...") disagrees. Somewhere a client computed a retry delay of 300 million seconds and scheduled a retry for a year none of us will be working in — the scheduler did not error, it merely complied, which is what makes schedulers terrifying. The specimen tests whether your backoff parses the full spec or the half of it you remembered. Also whether it sanity-checks the resulting delay, because a Retry-After measured in geological time should probably be treated as "this endpoint is done with you" rather than a literal instruction.
Replay it
curl -i https://faultydata.com/r/FD-2026-041
// response appears hereSignature
{Status:503 Headers:map[Retry-After:Sun, 01 Jan 2034 00:00:00 GMT] Body:{"error":"service unavailable","retry_after":"2034-01-01T00:00:00Z"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-019 — JSON body, text/plain label FD-2026-038 — Lying rate-limit headers FD-2026-073 — Retry-After: 0 (storm bait) FD-2026-086 — charset=utf-16 lie on a UTF-8 body FD-2026-100 — Conflicting duplicate Content-Length headers FD-2026-102 — Rate-limit headers that lie