httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <>
Subject Re: Mod_proxy_http override
Date Tue, 24 Mar 2009 21:30:29 GMT
Dingwell, Robert A. wrote:

> Getting to Step Two means that it found an address and Step Two itself is
> going to attempt to make the initial connection to that address.  My issue
> then comes into play where the address of a server is known but the server
> could refuse the connection on a particular port for some reason such as the
> site is down, or whatever.   If this happens and Apache is configured to
> ProxyRequests, the status is set to HTTP_NOT_FOUND, which really isnt the
> case, the server refused the connection it's not that the page wasn't found.

I ran into this recently, I suspect this is definitely a bug.

> Am I mistaken is thinking that r->proxyreq == PROXYREQ_PROXY  is always true
> when ProxyRequests is set to On in the configuration? If so how do I force
> the HTTP_SERVICE_UNAVAILABLE instead of the HTTP_NOT_FOUND? Do I have to
> patch this myself and recompile it?

Potentially you could patch it and submit it for inclusion into the 
server, at which point you won't need to worry about patching it again 
in the future.


View raw message