C.1 Error status codes returned by the Web container
When the client accesses a non-existent resource or a servlet in which an exception occurred, the Web container returns an error status code. The following table describes the error status codes returned by the Web container, and the conditions for returning the error status codes.
|
Error status codes |
Conditions for returning the error status code |
|---|---|
|
400 Bad Request |
Error status code 400 is returned when any of the following conditions are met:
|
|
401 Unauthorized |
The error status code 401 is returned when a resource that requires Basic authentication is accessed as follows:
|
|
403 Forbidden |
Error status code 403 is returned when any of the following conditions are met:
|
|
404 Not Found |
Error status code 404 is returned when any of the following is accessed:
|
|
405 Method Not Allowed |
Error status code 405 is returned in the case of an access that satisfies all of the following three conditions:
|
|
412 Precondition Failed |
Error status code 412 is returned, when the static contents that do not match the conditions specified in If-Match header or If-Unmodified-Since header, are accessed. |
|
413 Request Entity Too Large |
Error status code 413 is returned when the size of the request body exceeds the upper-limit value. |
|
416 Requested Range Not Satisfiable |
Error status code 416 is returned, when the static contents that use the value of an invalid Range header applicable to any of the following cases, are accessed:
|
|
500 Internal Server Error |
Error status code 500 is returned when any of the following conditions are met:
|
|
501 Not Implemented |
Error status code 501 is returned, when the static contents or the servlet that inherits javax.servlet.http.HttpServlet is accessed by an HTTP method other than the GET, HEAD, POST, PUT, DELETE, OPTIONS, and TRACE method. |
|
503 Service Unavailable |
Error status code 503 is returned when any of the following conditions are met:
|
- #1
-
Applicable when the Web application is version 2.4 or later.
- #2
-
This applies to the case when the port number of the https, used by the URL an access is forwarded to, is not set for the webserver.connector.redirect_https.port key in usrconf.properties.
- #3
-
Applicable when the version of the Web application is 2.4 or later, and javax.servlet.UnavailableException indicating the permanent unavailability occurs, and the exception is not caught in the servlet and JSP file.
- #4
-
Applicable in the following cases:
-
When the version of the Web application is 2.4 or later
When exception is not caught in servlets or JSPs
-
When the version of the Web application is 2.3
When the error page is not specified in the <error-page> tag of web.xml, or in the page directive of a JSP file, and the exception is not caught in the servlet or JSP file
- #5
-
Applicable when the reload functionality of the Web application, re-compilation functionality of the JSP file, or the reload functionality of J2EE application is not used.
- #6
-
Applicable when the <role-name> element is defined in the <auth-constraint> element of web.xml, and the <login-config> element is not defined. If the application is started in this state, warning message KDJE39150-W is output to the console window, and in the message log.
- #7
-
Applicable when the settings to control the number of concurrently executing threads in the Web application, or in the URL group are specified.
- #8
-
Applicable in the following cases:
-
When the version of Web application is 2.4 or later
When javax.servlet.UnavailableException indicating the temporary unavailability occurs, and the exception is not caught in the servlets or JSPs
-
When the version of Web application is 2.3
When the error page is not specified in <error-page> tag of web.xml, or in the page directive of JSP file, and the exception is not caught in the servlet or JSP file