https://bz.apache.org/bugzilla/show_bug.cgi?id=69803
--- Comment #3 from [email protected] --- Hi Mark, thanks for your response. I reviewed the Tomcat 9.0.107 release notes and noticed the following change: Fix: Allow the default servlet to set the content length when the content length is known, no content has been written and a Writer is being used. (markt) We believe this change is directly related to the issue we’re observing. After upgrading from 9.0.106 to 9.0.107 / 9.0.108, we consistently encounter: Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH Specifically: Tomcat sets Content-Length: 5243 but only 5206 bytes are actually delivered. Chrome/Edge fail with ERR_CONTENT_LENGTH_MISMATCH, while Firefox still accepts the response. The discrepancy is consistently 37 bytes, regardless of the request. This strongly suggests the regression is linked to how the connector now sets the Content-Length header when using a Writer before content is actually flushed/encoded. -- 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]
