ethan mindlace fremen wrote: > > > >2) Next, we should hack the Apache error page to be meaningful. For > > > >instance: > > If anyone knows how I trap for the "proxy not responding" error message, > I'd be happy to set something up, but I currently haven't the foggiest > idea. Stephen Harrison here at NIP has doen somethign similar for us... Steve? Chris