https://bz.apache.org/bugzilla/show_bug.cgi?id=69982
--- Comment #2 from Phil Clay <[email protected]> --- Thanks for taking a quick look! This morning I also took a look at the diff between 10.1.52 and 11.0.18, and while I did see some changes in the TLS handling, nothing really stood out to me as a problem. ------ I've tried a couple other Java versions as you suggested. I also tried an older Ubuntu version. I got the same results regardless of the Java/Ubuntu version. Specifically: Tomcat 11.0.18 Temurin-17.0.18+8 Ubuntu 24.04.04 - problem occurs Tomcat 11.0.18 Temurin-17+35 Ubuntu 20.04.3 - problem occurs Tomcat 10.1.52 Temurin-17.0.18+8 Ubuntu 24.04.04 - problem does not occur Tomcat 10.1.52 Temurin-17+35 Ubuntu 20.04.3 - problem does not occur I can try more if you think it would help, but at this point it doesn't look related to Java/Ubuntu versions. ------ I also attempted a workaround. I added a filter that set the "Connection: close" response header if response content-length > 50k. I figured closing the connection would force the remaining portion of the response to be sent. Unfortunately, it did not. Instead of having a delayed response, curl reported the following: curl: (18) transfer closed with 9805 bytes remaining to read So it seems like the server closed the connection without flushing the response completely. -- 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]
