What this tests

headerssemantics

Point your client at this specimen and find out — before prod does — whether it reads the headers, or just the status code.

Anatomy

The Date header says 1998. The response is fine, the body is fine, the data is current — but the server's clock thinks it's the year of the Tamagotchi, and every cache decision your client makes from this Date will be wrong by a quarter of a century. Freshness calculations go negative. Expiry math produces the Pliocene. Clock skew on the server side is depressingly common — VMs that resume from snapshots, containers without NTP, embedded devices counting time since an epoch nobody remembers choosing. The response is honest in every way except temporally. Clients that trust the Date header for cache validation will either cache this response forever or discard everything as prehistoric — both wrong, both confident. The correct move is comparing server Date to local time and distrusting deltas that span decades, which is also solid advice for humans.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Date:Mon, 02 Nov 1998 00:00:00 GMT] Body:{"status":"operational","served_at":"now-ish"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-069 — Unsolicited 304 to an unconditional request FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-019 — JSON body, text/plain label FD-2026-038 — Lying rate-limit headers FD-2026-041 — Retry-After as HTTP-date FD-2026-054 — Stale cache serving yesterday's answer