[Bug 60073] New: mod_proxy and ProxyRemote seems to do direct Connections in 503 Backend errors

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60073

Bug ID: 60073
Summary: mod_proxy and ProxyRemote seems to do direct
Connections in 503 Backend errors
Product: Apache httpd-2
Version: 2.2.31
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy
Assignee: ***@httpd.apache.org
Reporter: ***@fv.nrw.de

We have setup Apache with mod_proxy, requests to http://10.10.1.1/application
should be internal proxied/forwarded to http://10.10.2.1:57211/app

ProxyRequests Off
ProxyRemote * http://10.10.1.2:8084

ProxyPass /application http://10.10.2.1:57211/app
ProxyPassReverse /application http://10.10.2.1:57211/app


Special use case is, that the requests have to be forwareded through Firewall
and squid-proxy.

-> 10.10.1.1/application (Apache) -> Firewall -> 10.10.1.2 (squid Proxy) ->
10.10.2.1:57211/app (target Apache)


We now have one error Situation:

if there is an error 503 (backend error?) i see the following lines in
error_log

[Wed Aug 31 06:13:43 2016] [error] [client 10.10.1.50] proxy: Error reading
from remote server returned by /application
[Wed Aug 31 06:16:52 2016] [error] (110)Connection timed out: proxy: HTTP:
attempt to connect to 10.10.2.1:57211 failed
[Wed Aug 31 06:16:52 2016] [error] ap_proxy_connect_backend disabling worker
for (10.10.2.1)


the Problem now is: if there is an error 503 my Apache seems to try to directly
Access the backend. in this case i get an error_log in the Firewall and the
request is dropped.

how can i prevent mod_proxy with proxyremote directive to not in any case try
to connect direct. it should allways try to use the squid-proxy. even if there
is a backend or (squid-)Proxy error.

Markus

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60073

William A. Rowe Jr. <***@apache.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |MassUpdate
Resolution|--- |LATER
Status|NEW |RESOLVED

--- Comment #1 from William A. Rowe Jr. <***@apache.org> ---
Please help us to refine our list of open and current defects; this is a mass
update of old and inactive Bugzilla reports which reflect user error, already
resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all
development and patch review of the 2.2.x series of releases. The final release
2.2.34 was published in July 2017, and no further evaluation of bug reports or
security risks will be considered or published for 2.2.x releases. All reports
older than 2.4.x have been updated to status RESOLVED/LATER; no further action
is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd
feature, an unexpected server behavior, problems building or installing httpd,
or working with an external component (a third party module, browser etc.) we
ask you to start by bringing your question to the User Support and Discussion
mailing list, see [https://httpd.apache.org/lists.html#http-users] for details.
Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that
you retest using a modern httpd release (2.4.33 or later) released in the past
year. If it can be reproduced, please reopen this bug and change the Version
field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the
current httpd server software release is greatly appreciated.