From a high level, whats the difference between a webapp thats stopped
and a webapp thats undeployed?
One could call stopped a special scenario. In the past - a 503 was
returned to the user. Now its a 404. IIRC ... it changed to 404 as part
of a bug report but maybe that is the wrong change to make. (Too lazy to
look up the bug report)
[Personally - I'd rather stick apache in front let apache trap the
condition during the outage window and not worry about the rest.]
-Tim
Caldarale, Charles R wrote:
From: Tim Funk [mailto:funk...@apache.org]
Subject: Re: Custom 404 page when webapp stopped
From a user point of view, if I have an app (which is not the root
webapp) and I stop it, then all requests should then go to the root
webapp.
Is that really true? If the webapp is undeployed, I can understand that
unmatched requests will be handled by ROOT, but a stopped webapp is still known
to Tomcat, just not available.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
