What this tests
semanticsparsing
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
HTTP 207 — Multi-Status, WebDAV's contribution to the "success is a spectrum" school of API design — means some of your operations worked and some didn't, and the response contains a per-item verdict because one status code couldn't handle the emotional complexity. Batch APIs, bulk imports, and anything that does N things when you asked for N things lives here. The trap: clients that read the outer status see 207, file it under "success-ish", and move on — while three of their ten items 404'd inside the body, unprocessed, unalerted, quietly missing like the last items in a corporate goat-herding inventory. The envelope lied by aggregation. Correct behaviour: parse the envelope, iterate the per-item statuses, treat partial failure as partial failure. Incorrect behaviour: `if resp.ok`, which in a 207 world is optimism wearing a boolean.
Replay it
curl -i https://faultydata.com/r/FD-2026-068
// response appears hereSignature
{Status:207 Headers:map[Content-Type:application/xml; charset=utf-8] Body:<?xml version="1.0"?><multistatus><response><href>/item/1</href><status>HTTP/1.1 200 OK</status></response><response><href>/item/2</href><status>HTTP/1.1 404 Not Found</status></response><response><href>/item/3</href><status>HTTP/1.1 423 Locked</status></response></multistatus> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-066 — Captive portal interception (HTTP 511) FD-2026-067 — Legally unavailable (HTTP 451, geo-block) FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-035 — Stack trace in the error body FD-2026-047 — Guru Meditation (Varnish cache failure)