httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37770] - proxy: error reading status line from remote server (null)
Date Mon, 10 Dec 2007 10:32:37 GMT
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 asm@uezku.kemsu.ru  2007-12-10 02:32 -------
(In reply to comment #75)
> 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.
> 

If after FIN was recieved RST is following couldn't we assume that our request 
is sure rejected by remote server's TCP/IP stack?

Besides, I suppose that any client will suffer from such Byzantine problem. 
Where is the difference between mod_proxy and browser behaviour addressing 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


Mime
View raw message