Maurice 8c6157aa46 test(server): pin the request id through the body parsers ...

A handler behind express.json() is reached from the request stream's 'end'
event, long after the correlation middleware returned, so it looked as if
every write lost its id. It does not: raw-body and multer bind their
callbacks with AsyncResource at the point they are called, which is inside
the request's correlation. Nothing tested that, though, because every
REQID case was a GET. REQID-007 posts a JSON body and REQID-008 one that
arrives in several chunks, and both expect the handler to see the id the
response carries. The middleware comment now says why this holds.

2026-10-08 18:41:01 +02:00

..

globalMiddleware.correlation.test.ts

test(server): pin the request id through the body parsers

2026-10-08 18:41:01 +02:00

globalMiddleware.cors.test.ts

refactor(server): give every environment variable one config owner

2026-10-08 18:40:15 +02:00

globalMiddleware.csp.test.ts

feat(tours): add non-motorized day tour planning

2026-10-04 12:59:55 +02:00

globalMiddleware.redaction.test.ts

feat(notifications): Web Push delivers notifications to every device, even with TREK closed

2026-09-24 23:17:03 +00:00