What this tests

parsingauthsemantics

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

Anatomy

Your session expired somewhere in the middleware and the request you made — the one asking for JSON — has been answered with a 302 to a login page, or, worse, a 200 containing a fully-rendered HTML login form. The API is fine. The data is fine. You have simply been escorted to a completely different building and handed a form. This is the signature of session-based auth on an API that pretends to be stateless, which is to say most enterprise integrations. The client asked for data and received a username/password field, like a letter that arrived containing a raffle ticket to a different continent. The status code says 200. The Content-Type says text/ html. The body says "please sign in". Clients that check Content-Type survive. Clients that parse status codes and bodies on faith store a login page in their database, where it remains until someone queries "why is the customer_name field an HTML document" — a real thing that has really happened, repeatedly, at companies whose names you know.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:text/html; charset=utf-8] Body:<html><body><h2>Sign in to continue</h2><form method="post"><input name="username"/><input name="password" type="password"/><button>Sign in</button></form></body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-013 — Wrong types in a valid envelope FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern) FD-2026-035 — Stack trace in the error body FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) FD-2026-072 — Success response confirming the wrong values FD-2026-087 — 200 OK, body never arrived