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=42190>. 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=42190 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW ------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 18:33 ------- (In reply to comment #1) > How is this a bug? > > Or in other words, how would you expect the server to behave when a script > times > out or crashes, having already sent the headers? Well, Apache 1.3 behaviour was changed to return a proper HTTP reply (as per the other mentioned BugID #35424). I'm finding that applications I'm using - because they don't receive a proper HTTP reply are subsequently retrying and this is causing issues. I guess the other part that irks me is that this was handled correctly under Apache 1.3 and now is not consistent with that sort of expected response in Apache2.x >From the HTTP/1.1 RFC (2616), it looks as though the retry if connection closed is a proper behavior. I just don't believe that closing the connection under a timeout condition is the best response - Particularly given that this is likely to cause a retry. In either case, it's my belief that the server should respond with a '504 Gateway Timeout' under both Apache 1.3 and 2.x (though oddly enough Apache1.3 returns a '200 OK' with the previous bugID mentioned - which seems flawed to me). -- 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]
