https://bz.apache.org/bugzilla/show_bug.cgi?id=69803
Mark Thomas <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Mark Thomas <[email protected]> --- This does not occur on a clean Tomcat 9.0.x install with resources with a range of content lengths. At this point this looks more like an application issue than a Tomcat issue. I'll note that if Tomcat's HTTP/1.1 was this fundamentally broken, there would be many, many more users reporting issues. The root cause analysis is not analysis. It is speculation at best and adds nothing to the report. The steps to reproduce the issue don't. This further suggests an application issue. For the Tomcat team to look at this you will need to provide a reproducible test case. This should take the form of the minimal web application (WAR with source) that demonstrates the issue on a clean install of the latest Tomcat 9.0.x release (or the latest release of any other currently supported version). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
