DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43929>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43929 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2008-01-08 12:17 ------- I can see a pettern here, taht let's me reopen the issue. We actually send the include as a GET with a Content-Length header "3" and no body. The length "3" might come from the main request, because the main request is a POST with body "x=y" of length "3". So it should be normal for Tomcat to wait for the body. It is interesting though, that the log contains a couple of calls to the same URL, and whenever the included request with the buggy content length is sent via a freshly opened connection, it succeeds... I'll investigate, why we use the content length of the main request for the included GET, could also be a mod_include bug. Let's see. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
