Secure Error Handling 2D: Stack Trace Leak vs. Sanitized Response Diagram

Requests stream through a client → gateway → service → database schematic pipeline, and a fraction of them fail at the service node. This simulator lets you flip the error handler between two real-world contracts: a verbose one that returns the raw exception — stack trace, connection string, query text — straight to the caller, and a sanitized one that returns a generic message plus a correlation ID while the real detail is written only to a centralized log store. Drag the diagram to pan and scroll to zoom, watch leaked-secret packets (red) fly all the way back to the client under the insecure mode versus sanitized packets (green) paired with a log entry (yellow) under the secure mode, tick individual payload fields on or off to see the field-exposure tally track exactly what a partially-hardened handler still forgets to strip, and read the exposure score live on the scrolling strip chart underneath.