https://issues.apache.org/bugzilla/show_bug.cgi?id=50906
--- Comment #1 from Chris <ch...@blaze.io> 2011-03-10 12:50:01 EST --- I'm including some additional info that I'd posted to the mailing list: - I'm running with nginx in front of tomcat - The 60 second timeout is happening in nginx and not tomcat - Regardless of whether or not I'm using libtcnative, I don't see the terminating "0\r\n\r\n" being sent by tomcat to nginx - When not using libtcnative, the connection is closed after writing the response; there's a FIN, in addition to ACK on the last TCP packet from tomcat. Nginx seems to use this to infer the end of the response and add the "0\r\n\r\n" to the reply sent to the client. - When using libtcnative, there is no FIN on the last TCP ACK packet, and the connection stays open. One minute later nginx times out waiting for the response to complete and adds the "0\r\n\r\n" to the response to the client. - I notice that if I use curl to make a request directly to tomcat (instead of going through nginx), then I do see the terminating "0\r\n\r\n". I still see a difference in that tomcat disconnects immediately after the reply when not using the native library. Later I said...: I've narrowed this down even further. As I mentioned below, the "0\r\n\r\n" was not being sent to nginx, although it was being sent to curl. The difference was that nginx was doing a GET HTTP/1.0, while curl was using HTTP/1.1. If I configure curl to use HTTP/1.0 then I get the same result: no "0\r\n\r\n" is sent. So, to summarize: - GET HTTP/1.0 results in no terminating "0\r\n\r\n" for the chunked response, regardless of whether libtcnative is being used. - The difference when using libtcnative is that the connection isn't terminated after the response is sent. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
