Status codes in use

If the page is displayed correctly in the browser, this status code will be returned in most cases.

Example: When a request to create a resource using the PUT method is made, this code is returned on completion of that request.

Example: When a request to create a resource using the PUT method is made, this code is returned when the server has accepted the request but creation of the resource has not been completed. For batch processing.

This code is returned when a client request is abnormal (such as using an undefined method).

Used when performing Basic or Digest authentication. Most browsers display an authentication dialog when this status is returned.

This code is returned in cases such as the user not having access privileges, or the host received a banned request.

Example: An attempt is made to access a page from outside the company when access to that page is only allowed internally (intranet).

This code is also used when the user simply does not have access privileges.

Example: When the POST method is used at a location where use of the POST method is not permitted.

Example: The server can only accept English or Japanese, however, only zh (Chinese) is included in the Accept-Language: header of the request.

Example: The server tried to send an application/pdf document, however, application/pdf was not included in the Accept: header of the request.

Example: The server tried to send text in UTF-8 format, however, uft-8 was not included in the Accept-Charset: header of the request.

This code is returned when a request is not completed within a specified time.

The request cannot be completed due to a conflict with an existing resource.

The file was moved permanently. Its location is unknown.

This code is similar to 404 Not Found, however, it indicates that the file will not be recovered.

This code is returned when a precondition is false.

Example: When an update occurs after the time when the If-Unmodified-Since: header of the request was written.

Example: When an attempt was made to send data that exceeded the upper limit of the uploader.

Example: When an attempt is made to send large data such as image data using the GET method, and the URI is tens of KB in length (the upper limit depends on the server).

For example, when an attempt is made to retrieve 1025 Bytes, yet the size of the resource is only 1024 Bytes.

The extension cannot be responded to, or the proxy server deems that the next server to receive a request cannot respond.

As a specific example, when an unusual value other than 100-continue is entered in the Expect: header, or the server cannot handle 100 Continue in the first place.