DO NOT REPLY [Bug 38763] - mod_proxy does not handle asynchronous connection close correctly

[bu...@apache.org]

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=38763>.
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=38763





------- Additional Comments From rpluem@apache.org  2006-02-23 22:03 -------
I admit that the current behaviour is not convenient, but I see no RFC violation
here. Please read the next two sentences in the RFC after

"This means that clients, servers, and proxies MUST be able to recover from
asynchronous close events."

The next two sentences say:

Client software SHOULD reopen the transport connection and retransmit the
aborted sequence of requests without user interaction so long as the request
sequence is idempotent (see section 9.1.2). Non-idempotent methods or sequences
MUST NOT be automatically retried, although user agents MAY offer a human
operator the choice of retrying the request(s).

The proxy can be seen as client in this case. 
1. There is no MUST for the client to retransmit if the request is idempotent.
2. If the request is not idempotent like POST it MUST NOT retransmit.
3. There is no definition what "recover" means. I see sending a Bad Gateway
response as some sort of recover from this situation.

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org