Bug 60073 - mod_proxy and ProxyRemote seems to do direct Connections in 503 Backend errors
Summary: mod_proxy and ProxyRemote seems to do direct Connections in 503 Backend errors
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.2.31
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2016-08-31 13:54 UTC by Markus
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Markus 2016-08-31 13:54:42 UTC
We have setup Apache with mod_proxy, requests to should be internal proxied/forwarded to

ProxyRequests Off
ProxyRemote *

ProxyPass /application
ProxyPassReverse /application

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

-> (Apache) -> Firewall -> (squid Proxy) -> (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] 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 failed
[Wed Aug 31 06:16:52 2016] [error] ap_proxy_connect_backend disabling worker for (

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.

Comment 1 William A. Rowe Jr. 2018-11-07 21:09:59 UTC
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.