What this tests

parsing

Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.

Anatomy

The response ends mid-object, mid-string, mid-thought — a JSON body that simply stops, like a phone call into a tunnel. Content-Length promised more; the socket delivered less; what you got was the first 40% of a perfectly good payload followed by the digital equivalent of a dial tone. Every parser handles this differently, and every difference is a bug report. Some throw. Some return partial objects — the truly sinister outcome, where the first three fields of a ten-field record look perfectly healthy and get committed to a database with the quiet confidence of a man walking off a cliff he can't see. Your options: validate the whole envelope before trusting any of its contents, or become the kind of person who explains to an auditor why half the records in the ledger are haikus.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[] Body: Corrupt:truncate Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-012 — Malformed JSON (trailing comma) FD-2026-013 — Wrong types in a valid envelope FD-2026-014 — Encoding mismatch (claims UTF-8, sends Latin-1) FD-2026-015 — UTF-8 BOM prefix FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024) FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern)