DO NOT REPLY [Bug 51106] Error page handling serves most general exeptions first
https://issues.apache.org/bugzilla/show_bug.cgi?id=51106 Karl San Gabriel changed: What|Removed |Added CC||karl.sangabr...@gmail.com OS/Version||All -- 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 51116] New: stopped virtual host replies with 400 Bad Request
https://issues.apache.org/bugzilla/show_bug.cgi?id=51116 Summary: stopped virtual host replies with 400 Bad Request Product: Tomcat 6 Version: 6.0.32 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: dev@tomcat.apache.org ReportedBy: akostadi...@gmail.com When a virtual host is stopped in tomcat 6 and client tries to access it, tomcat replies with 400 Bad Request. Here you can find a patch that should change this behavior to send 404 instead (which in my opinion makes more sense): https://issues.jboss.org/secure/attachment/12336975/standardenginevalvetomcat6.0.24-jbpapp3775.patch -- 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
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: akostadi...@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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
