On Nov 26, 2007 6:41 PM, Robert Granvin <Robert.Granvin@xxxxxxxxxxxxxx> wrote: > > > Not sure that's a particularly descriptive subject ... > > What we're facing here is a simple situation, but not so clear of a > solution. Perhaps this is easy and/or someone can offer me suggestions from > past experience? > > Basically, our primary web server has a link to an important, well used, web > site that resides on a physically different server (we have root access to > both, by the way, so configuration changes are possible). > > When the remote web server is down/unavailable, we want the link to failover > to a catch-all page that gives alternate access temporarily to important > pieces. > > The second scenario is that the remote web server itself is up, but the > application running (jboss in this case) is down or non-responsive. We want > to accomplish the same thing. > > My guess is that the first one is a lot easier than the second. :-) I'm > not sure if #2 is as easy as creating a custom 404 page. I guess what you need is a custom 500 page. eg. ErrorDocument 500 /falbacksite/index.html Krist -- krist.vanbesien@xxxxxxxxx krist@xxxxxxxxxxxxx Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx