What this tests
semanticsheaders
Point your client at this specimen and find out — before prod does — whether it interprets status codes and content types correctly, or makes things up.
Anatomy
You sent a plain GET. The server, possessed of a cache with opinions, answered 304 Not Modified — a status that is only legal as an answer to a conditional request you didn't make. No body, because 304s don't have bodies. Your client sent nothing to compare it against; it asked for the data and was told, essentially, "you already have it", when it very much did not. This happens in the wild wherever a middlebox "optimizes" caching semantics it doesn't understand — proxies that convert responses, CDN rules that cache by path and ignore request headers, an edge that was configured by someone who'd read half the RFC. Usually half. The half that seemed important. Delivered via raw HTTP because most HTTP frameworks refuse to produce it, which is telling. Clients that treat 304 as "use my cache" will use an empty cache — an item that exists, is empty, and is wrong, which is also a description of several enterprise databases.
Replay it
curl -i https://faultydata.com:8443/r/FD-2026-069
This exhibit breaks the connection itself, so replay it on the direct line (port 8443), where nothing sits between you and the bytes. On the main site the web server in front tidies the wreckage into a polite 502, and the button below will show you exactly that.
// response appears hereSignature
{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw:HTTP/1.1 304 Not Modified
Content-Length: 0
X-Fault-Specimen: FD-2026-069
Phases:[]}
Keep digging
FD-2026-076 — Date header from the distant past 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