What this tests
headersparsing
Point your client at this specimen and find out — before prod does — whether it reads the headers, or just the status code.
Anatomy
Two Content-Length headers, two different values. HTTP/1.1 has rules for this — RFC 7230 says reject it — but "says reject it" and "your stack rejects it" are separated by an implementation detail that has powered a decade of request-smuggling CVEs. One parser reads the first, another reads the second, and suddenly your proxy and your backend disagree about where the request ends. Written raw, past Go's civilised header handling, because a conforming HTTP stack literally cannot emit this — which is the whole point.
Replay it
curl -i https://faultydata.com:8443/r/FD-2026-100
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 200 OK
Content-Length: 5
Content-Length: 64
Content-Type: application/json
Connection: close
{"id":1,"name":"what the proxy saw != what the backend saw"} Phases:[]}
Keep digging
FD-2026-019 — JSON body, text/plain label FD-2026-041 — Retry-After as HTTP-date FD-2026-086 — charset=utf-16 lie on a UTF-8 body FD-2026-036 — Content-Encoding lie (gzip header, plain body) FD-2026-039 — XML where JSON was promised FD-2026-052 — JSONP callback wrapper