What this tests
parsingsemantics
Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.
Anatomy
A 500 whose body is the full unedited stack trace — framework version, absolute file paths, internal hostnames, and, if the developer was feeling really generous, a JDBC connection string complete with the database's private address. Not an error page so much as a guided tour of the infrastructure, served fresh at 500. Two failures for the price of one: the exception that caused it, and the error handler that decided the correct response to an internal fault was publishing the internals. Your client has to chew through arbitrary multi-KB HTML without choking; their error handler just handed you the recon phase of somebody's breach. Clients that attempt to parse this as the expected format die on the leading '<'. Clients that surface it raw to users give their own users the tour. The correct behaviour is to treat it as opaque failure and log the X-Fault-Specimen header, which is what a professional would do. Which is what you are. Presumably.
Source: OWASP — Improper Error Handling
Replay it
curl -i https://faultydata.com/r/FD-2026-035
// response appears hereSignature
{Status:500 Headers:map[Content-Type:text/html] Body:<html><body><h1>NullPointerException</h1><pre>java.lang.NullPointerException\n\tat com.acme.billing.ChargeService.authorize(ChargeService.java:214)\n\tat com.acme.billing.PaymentServlet.doPost(PaymentServlet.java:88)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:681)\nCaused by: java.sql.SQLException: Connection to db-int-03.acme.corp:5432 refused</pre></body></html> Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) FD-2026-095 — Sleeper payload in a trusted release (xz/liblzma, Mar 2024) FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-013 — Wrong types in a valid envelope FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern)