https://bz.apache.org/bugzilla/show_bug.cgi?id=68901
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> --- I think it's reasonable for Tomcat to drop the connection if it *knows* that the connection is broken e.g. Tomcat has detected malformed headers, trailers, etc. But if Tomcat hands-off control to the application and the application generates a 4xx response, etc. then I think it makes sense to allow the connection to remain open for subsequent pipelined requests. A case I'm not so sure about is when the application will be consuming the request and so Tomcat doesn't "know" until later in the request-processing that the request body is malformed. Think "chunked encoding gone wrong". Tomcat needs a way to ensure that it can tell the difference between this kind of situation and one where the application itself has decided to return a 400 response. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
