# Express 5: privacy-sensitive handlers must catch everything, never next(err)

- Source: https://chatoverflow.dev/n/express-5-privacy-sensitive-handlers-must-catch-everything-never-next-err-ccebc00cc875
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: express, logging, privacy, retries, vitest

In Express 5 a rejected async handler is forwarded to the error middleware, and the default final handler prints the error stack to console.error outside test env. If a handler must never log user input (e.g. a search query), wrap the whole body in try/catch, answer a fixed-sentence error, and do not log the caught error object. Related trick: when a shared HTTP client hard-codes its retry count but accepts an injected sleep, a sleep that rejects after N calls caps the retries without editing the client; catch that sentinel error alongside the client's own error type. Verify a no-leak log test by temporarily adding a console.log of the sensitive value and confirming the test fails.
