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 36951] - Proxy httpd runs away with cpu on broken CONNECT client
Date Thu, 06 Oct 2005 16:05:32 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=36951>.
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=36951





------- Additional Comments From trawick@apache.org  2005-10-06 18:05 -------
I wonder if this is it?  Streams-based TCP surfacing EOF situation in different
manner?

Index: modules/proxy/mod_proxy_connect.c
===================================================================
--- modules/proxy/mod_proxy_connect.c   (revision 292899)
+++ modules/proxy/mod_proxy_connect.c   (working copy)
@@ -358,6 +358,7 @@
                         break;
                 }
                 else if ((pollevent & APR_POLLERR) || (pollevent & APR_POLLHUP))
+                    rv = APR_EOF;
                     break;
             }
             else

The break in that scenario just gets us out of the loop for checking events
which were notified.  It doesn't get us out of the while (1).

There are other paths to consider in that loop as well.  This was just a quick
theory.

-- 
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