> On Aug 11, 2024, at 07:50, Itzhak Fadida <itzhak.fad...@plainid.com.INVALID> > wrote: > > I’m reaching out to see if anyone else has encountered an issue with > chunked transfer encoding in Tomcat versions 10.1.25 to 10.1.28 when > used with a Spring-based application. > > Issue Summary: > > • Problem: Chunked transfer encoding seems to behave incorrectly in > Tomcat versions 10.1.25 through 10.1.28. Specifically, instead of > receiving several chunks of data, I am receiving the entire message in > a single chunk, but only when the connection is closed by the client. > > • Expected Behavior: In previous versions, including 10.1.23 and > earlier, the application correctly received data in multiple chunks as > expected with chunked transfer encoding. > > • Observed Behavior: Since upgrading to Tomcat 10.1.25 and through > 10.1.28, it appears that data is being buffered and sent as a single > chunk when the connection is closed, rather than being sent in > multiple chunks during the transmission.
Thanks for the detailed analysis. However, my reading of the pertinent RFC (9112) indicates that chunked encoding is optional on responses where the content length is known. Do you have a different interpretation? This doesn’t explain why the observed behavior changed between 10.1.23 and 10.1.25, but it may well be allowed by the specs. - Chuck > Investigation: > > I reviewed the changelogs and noticed there were modifications related > to chunked transfer encoding in these versions. However, it’s unclear > whether these changes were intended to affect this behavior or if this > is a regression. > > Technical Details: > > • Tomcat Version: The issue is observed in versions 10.1.25, 10.1.26, > 10.1.27, and 10.1.28. > > • Spring Version: 3.3.2. > > • Configuration: The application uses chunked transfer encoding for > streaming responses, and it has been working correctly in earlier > versions of Tomcat. > > • Client Behavior: The client closes the connection after sending the > request, which previously led to the server processing and sending the > response in multiple chunks. Now, the server sends the entire response > as one chunk when the connection is closed. > > Request for Assistance: > > • Has anyone else experienced this behavior with chunked encoding in > these specific Tomcat versions? > > • Is this a known issue or an intended change in the way Tomcat > handles chunked responses? > > • Any suggestions for workarounds or configurations that could help > restore the correct chunked encoding behavior? > > I appreciate any insights or advice from the community. If additional > information is needed, I’m happy to provide it. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
