DO NOT REPLY [Bug 8613] New: - POST request with invalid Content-Length header

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8613>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8613

POST request with invalid Content-Length header

           Summary: POST request with invalid Content-Length header
           Product: Tomcat 4
           Version: 4.0.2 Final
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:JK/AJP (deprecated)
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: johan.welsch@atosorigin.com


USING: APACHE 1.3.17 + mod_jk.so

Some browsers seem to POST forms with invalid Content-Length headers (greater 
than the data really posted), then Apache waits for the missing datas. As soons 
as the client click on the 'stop' button or whatever that closes the socket 
between browser and server, one httpd process enters an infinite loop  with one 
Ajp13Connectector thread. Trussing the looping apache process, it looks like 
this :

6766/1:         send(7, "12 4\0\0", 4, 0)                       = 4
6766/1:         recv(7, " A B\003", 4, 0)                       = 4
6766/1:         recv(7, "061FFA", 3, 0)                         = 3

reading AJP protocol : Send me more data, sorry I've none left.
My quick and dirty hack was to pass my forms into GET method, and kill the 
looping httpd processes (it turned my production servers back into a stable 
behaviour, hopefully !).. I don't have any patch to submit, sorry.

Hope this helps

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>