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=37770>. 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=37770 ------- Additional Comments From [EMAIL PROTECTED] 2007-12-09 02:57 ------- (In reply to comment #74) > (In reply to comment #73) > > (In reply to comment #71) > > > Created an attachment (id=21243) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=21243&action=view) [edit] [edit] [edit] > > > backend connection race condition fix (untested) > > > > > > This should fix such race condition. > > > > As explained before this patch is not correct: > > > > 1. Once you sent the request body it is no longer available. > > This can be fixed. Not easily as buffering large request entities is a pain. > > > 2. The RFC does not allow to resend non idempotent requests. > > Why does this applies to our situation when the request does not reach > backend > server? With your loop you don't know. Once you sent a single byte of the request body or even only the GET request with parameters you do not really now what the backend server did. Didn't it receive it or did it receive it, processed it and just in the moment as it wanted to send the reply the network broke down or the process that processed the request died. -- 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]
