What this tests
parsingtimeouts
Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.
Anatomy
The API returns a 2MB JSON array where the client expected a record — technically valid, syntactically perfect, and large enough to make your buffer allocation question its life choices. Not truncated, not corrupted: just enormous, like a reply to "what time is it" that contains the history of horology. This is what pagination-free endpoints degrade into: a table that was twelve rows at launch and two million rows by year three, still faithfully serialized in full because nobody added a LIMIT clause and the frontend paginates client-side. The client-side part is doing a lot of work in that sentence. Clients that read the whole body before parsing will buffer 2MB for a payload they needed 200 bytes of. Clients that stream will get the first items early and can bail. Both are valid strategies; only one survives "the table grew".
Replay it
curl -i https://faultydata.com/r/FD-2026-084
// response appears hereSignature
{Status:200 Headers:map[] Body: Corrupt:huge Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-070 — Content-Length lies (body shorter than declared) FD-2026-081 — Response dies mid-headers FD-2026-011 — Truncated JSON body 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)