Len Popp wrote:
Yeah, I've done that; it works great for most users, including experienced IT people if they don't stop to look too close.I don't think you can do that. After Tomcat accepts the HTTP connection and decides whether to respond, it's too late to pretend there's no server there. The user's web browser displays a different error message for no server (something like "can't establish a connection") vs. server timeout (something like "the server took too long to respond") or dropping the connection ("the connection was reset").So you might as well just customize the 404 error page to say "There's no server here" - it'd fool people just as well. :-) Or just return an empty error page.
D --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
