You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2025/09/04 06:54:53 UTC
[Bug 69803] HTTP/1.1 Connector Content-Length header calculation regression causing Chrome/Edge net::ERR_CONTENT_LENGTH_MISMATCH
https://bz.apache.org/bugzilla/show_bug.cgi?id=69803
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org