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=21544>. 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=21544 Problem in uploading a large file when LimitRequestBody set in the httpd.conf file ------- Additional Comments From [EMAIL PROTECTED] 2003-12-19 01:28 ------- You'd have to verify this with a tusc trace, but I suspect that the child process got zapped with SIGALRM because it was taking too darn long to soak up the request body. After the SIGALRM, the connection gets closed by Apache before the client has necessarily seen the 413 response, so the browser puts up some sort of error. not so clear that soaking up the whole request body forever and ever is really the right thing to do just in case the user is still awake when the file is through getting uploaded to the bitbucket, though I understand that the message in the browser after the timeout/dropped-connection isn't so helpful either the real fix is for the browser to implement the "Expect: 100-Continue" protocol, let Apache respond "no way" before starting the upload, and things proceed normally; the unlimited-in-size request body doesn't have to get transferred over the network before the browser finally sees the error response --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
