No you misunderstood my post. I'm not an idiot, I understand the point of proxying, if the target server is down I won't be able to connect. Here's a more clear example. I'm proxying 2 http servers, server A and server B. If server B is not running when the proxy starts, I can't connect to server A. I receive this message in the browser
Bad Gateway The proxy server received an invalid response from an upstream server. as well as the error in the log I posted previously, but its not an error for the host I'm requesting with the browser! Its not clear to my why the proxy virtual hosts are not independent of each other. Is there another configuration directive I need? Todd On 11/25/06, paul <[EMAIL PROTECTED]> wrote:
Todd Nine schrieb: [snip] > Now, I am having a problem, and have a question. First if all of the > servers I am connecting to via the proxy server are not running, all of the > virtual hosts that I'm proxying fail with the following error message for > every back end server that's not running. This seems to cause all proxying > to fail. Wait, you're saying if the backend is down proxying fails? What a surprise... > > [Fri Nov 24 14:07:26 2006] [error] (113)No route to host: proxy: HTTP: > attempt to connect to 192.168.221.102:80 (192.168.221.102) failed > > How can I set up the virtual host proxy to not cause an error if it cannot > connect to the back end server? Second, how can I set up a default "the > server is under maintenance" page with the host name in it? I get a proxy error with a HTTP error code (cannot remember offhand). It should be possible to set up a custom error page to catch that. cheers Paul --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
