https://issues.apache.org/bugzilla/show_bug.cgi?id=57168
Bug ID: 57168
Summary: mod_proxy_connect - AH01026: err/hup on backconn
Product: Apache httpd-2
Version: 2.4.10
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_connect
Assignee: [email protected]
Reporter: [email protected]
I'm using Apache 2.4.10 on windows and am seeing these entries in the log every
now and then that seem to correspond to a failure to `HTTP CONNECT` properly.
[Thu Oct 30 13:42:03.964941 2014] [proxy_connect:notice] [pid 1992:tid 872]
[client 10.83.71.222:50028] AH01026: err/hup on backconn
[Thu Oct 30 13:42:53.716374 2014] [proxy_connect:notice] [pid 1992:tid 932]
[client 10.83.71.222:50018] AH01026: err/hup on backconn
[Thu Oct 30 13:42:53.950375 2014] [proxy_connect:notice] [pid 1992:tid 1036]
[client 10.83.71.222:50019] AH01026: err/hup on backconn
[Thu Oct 30 13:44:48.727707 2014] [proxy_connect:notice] [pid 1992:tid 924]
[client 10.83.71.222:50023] AH01026: err/hup on backconn
[Thu Oct 30 13:44:48.727707 2014] [proxy_connect:notice] [pid 1992:tid 976]
[client 10.83.71.222:50022] AH01026: err/hup on backconn
This seems to correspond almost exactly with bug #56299 on mod_proxy_ws_tunnel.
The code that was patched there looks suspiciously similar to the code in
mod_proxY_connect that is causing this error message to show up for me. Is the
issue that was fixed there also present and needs to be fixed in
mod_proxy_connect as well? Or is there a reason to fix it only in
mod_proxy_ws_tunnel?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
