C.2 Error status codes returned by the Redirector

When a timeout occurs during a data transaction with the Web container, and when the coding of the definition file contains an error, the redirector returns an error status code. The following tables describe the error status codes returned by the redirector and the conditions for returning the error status code, for each type of Web server.

Table C‒3: Error status codes returned by the redirector and the occurrence conditions (for Cosminexus HTTP Server)
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: When the port number of Host header of the request is invalid When the request method is not `POST`^#1 When the request does not have a Content-Length header (for a POST request, the body is a chunk format)^#1 When the Content-Length header value of the request exceeds the upper limit of the POST data size set in the POST request sending destination worker^#1
500 Internal Server Error	Error status code `500` is returned when any of the following conditions are met: When there is a coding error in the contents of `mod_jk.conf`^#2 When there is a failure in reading, or a coding error in the contents of `workers.properties`^#1 When the request header exceeds 16 KB^#3 When failed to establish connection with the Web container When timeout occurs during establishment of a connection to the Web container When an error occurs during sending data to the Web container When timeout occurs during sending data to the Web container When an error occurs during receiving data from the Web container When timeout occurs during receiving data from the Web container When timeout occurs in reading the POST data from the client When an unsupported HTTP method^#4 is specified in the request

#1: Applicable when the default worker is not specified in the distribution by the POST data size.
#2: Applicable only in Windows. The web server fails to start in UNIX.
#3: Might be applicable when a request header of a total size of 16 KB or more can be received according to the settings for limitations of request headers in Cosminexus HTTP Server.
#4: For details on whether the HTTP method is supported or not, see Table C-5.

Table C‒4: Error status codes returned by the redirector and the occurrence conditions (for Microsoft IIS)
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: When the request URL contains a (percent sign (`%`) and the two characters after the percent sign (`%`) do not express hexadecimals (characters other than A-F, a-f, or 0-9) When the port number of Host header of the request is invalid
403 Forbidden	Error status code `403` is returned when any of the following conditions are met: When the request URL begins with "`hitachi_ccfj`"^#1 When the request URL contains "`%2F`"^#1
500 Internal Server Error	Error status code `500` is returned when any of the following conditions are met: When there is a coding error in the contents of `isapi_redirect.conf` When there is failure in reading, or a coding error in the contents of `workers.properties` When the request header exceeds 16 KB^#2 When failed to establish connection with the Web container When timeout occurs during establishment of a connection to the Web container When an error occurs during sending data to the Web container When timeout occurs during sending data to the Web container When an error occurs during receiving data from the Web container When timeout occurs during receiving data from the Web container When timeout occurs in reading the POST data from the client When an unsupported HTTP method^#3 is specified in the request

#1: Not case-sensitive.
#2: Might be applicable when a request header of a total size of 16 KB or more can be received according to the settings for limitations of request headers in Microsoft IIS.
#3: For details on whether the HTTP method is supported or not, see Table C-5.

Support for the request HTTP methods in the redirector

The following table lists the request HTTP methods that are supported in the redirector.

Table C‒5: Support for the request HTTP methods in the redirector
HTTP method	Supported or not
`OPTIONS`	Y
`GET`	Y
`HEAD`	Y
`POST`	Y
`PUT`	Y
`DELETE`	Y
`TRACE`	Y
`CONNECT`	--^#
`PROPFIND`	Y
`PROPPATCH`	Y
`MKCOL`	Y
`COPY`	Y
`MOVE`	Y
`LOCK`	Y
`UNLOCK`	Y
`ACL`	Y
`REPORT`	Y
`VERSION-CONTROL`	Y
`CHECKIN`	Y
`CHECKOUT`	Y
`UNCHECKOUT`	Y
`SEARCH`	Y
Methods available in HTTP1.1 other than above-mentioned methods	--^#

Legend:

Y: Supported

--: Not supported

#

The redirector returns a status 500 error to a request that specifies an unsupported HTTP method. Furthermore, the message KDJE41001-E is output.

To Page Top