https://bz.apache.org/bugzilla/show_bug.cgi?id=68919
Bug ID: 68919
Summary: Make Tomcat return 503 on stopped web applications
Product: Tomcat 9
Version: 9.0.x
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: micha...@apache.org
Target Milestone: -----
This somewhat reverts or picks up Bug 51117.
When a webapp is deliberately stopped or failed to start Tomcat should respond
with 503 since the resource is known, but Tomcat isn't able to serve it. For
me, it is clearly a difference from 404.
On occasions I have to stop applications because upstream services aren't
available and my downstream clients shall rather see 503 in their logs. I think
it is in conformance with
https://www.rfc-editor.org/rfc/rfc9110.html#name-503-service-unavailable.
At least the behavior should be configurable whether the admin prefers 404 or
503 on a per app basis? Maybe something in context.xml or per Host?
--
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
