An issue exists where a single request can crash an application using default options. When a request uses a Content-Encoding like gzip, the software pipes it into a decompression stream but fails to attach an error listener after reading the body. If a payload contains one valid compressed frame followed by trailing bytes, the application responds normally to the valid frame, but the trailing bytes trigger an error in the finished decoder. This error is re-thrown as an uncaught exception, terminating the process. Since body parsing occurs before routing, any endpoint that parses a body is affected.