You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/04/26 07:58:28 UTC
DO NOT REPLY [Bug 51117] New: stopped deployment or virtual host
reply with error 503
https://issues.apache.org/bugzilla/show_bug.cgi?id=51117
Summary: stopped deployment or virtual host reply with error
503
Product: Tomcat 5
Version: 5.5.32
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: akostadinov@gmail.com
When a deployment or a virtual host is stopped in tomcat5, an access attempt is
replied to with:
HTTP Status 503 - This application is not currently available
Wouldn't 404 be better?
{quote}
The Http 500 category are server side errors. If a context or host isn't found,
it's a client error. Internally, there is no way to tell if the context exists
once it's been undeployed/stopped. The server, if the URL is syntactically
correct and lacking internal resources/configuration to do anything else,
should respond with HTTP404 (SC_NOT_FOUND).
{quote}
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 51117] stopped deployment or virtual host reply
with error 503
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51117
Konstantin Kolinko <kn...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
Severity|normal |enhancement
--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> 2011-04-26 03:47:55 EDT ---
(In reply to comment #0)
> When a deployment or a virtual host is stopped in tomcat5, an access attempt is
> replied to with:
> HTTP Status 503 - This application is not currently available
>
> Wouldn't 404 be better?
It is a matter of preference. 503 is some specific response status code
officially defined in RFC 2616. This is not an error to return 503 there.
Changing Severity and closing as WONTFIX, because this behaviour in Tomcat 5.5
will not be changed.
If I remember correctly, Tomcat 6 already replies with 404 when webapps are
stopped, thus this issues is "fixed" there.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org