# Status Code

Table 1 describes the status codes.

Table 1 Status code
Status Code | Code | Description
--- | --- | ---
100 | Continue | The server has received the initial part of the request and the client should continue to send the remaining part. It is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response.
101 | Switching Protocols | The requester has asked the server to switch protocols and the server has agreed to do so. The target protocol must be more advanced than the source protocol. For example, the current HTTP protocol is switched to a later version of HTTP.
201 | Created | The request has been fulfilled, resulting in the creation of a new resource.
202 | Accepted | The request has been accepted for processing, but the processing has not been completed.
203 | Non-Authoritative Information | The server successfully processed the request, but is returning information that may be from another source.
204 | NoContent | The server has successfully processed the request, but does not return any content. The status code is returned in response to an HTTP OPTIONS request.
205 | Reset Content | The server has successfully processed the request, but does not return any content. Unlike a 204 response, this response requires that the requester reset the content.
206 | Partial Content | The server has successfully processed a part of the GET request.
300 | Multiple Choices | There are multiple options for the requested resource. For example, this code could be used to present a list of resource characteristics and addresses from which the client such as a browser may choose.
301 | Moved Permanently | This and all future requests should be permanently directed to the given URI indicated in this response.
302 | Found | The requested resource was temporarily moved.
303 | See Other | The response to the request can be found under a different URI, and should be retrieved using a GET or POST method.
304 | Not Modified | The requested resource has not been modified. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.
305 | Use Proxy | The requested resource is available only through a proxy.
306 | Unused | This HTTP status code is no longer used.
400 | BadRequest | The request is invalid. The client should modify the request instead of re-initiating it.
401 | Unauthorized | The authorization information provided by the client is incorrect or invalid.
402 | Payment Required | This status code is reserved for future use.
403 | Forbidden | The server has received the request and understood it, but the server is refusing to respond to it. The client should modify the request instead of re-initiating it.
404 | NotFound | The requested resource cannot be found. The client should modify the request instead of re-initiating it.
405 | MethodNotAllowed | A request method is not supported for the requested resource. The client should modify the request instead of re-initiating it.
406 | Not Acceptable | The server cannot fulfill the request based on the content characteristics of the request.
407 | Proxy Authentication Required | This code is similar to 401, but indicates that the client must first authenticate itself with the proxy.
408 | Request Time-out | The server timed out waiting for the request. The client may re-initiate the request without modifications at any later time.
409 | Conflict | The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request.
410 | Gone | The requested resource cannot be found. The status code indicates that the requested resource has been deleted permanently.
411 | Length Required | The server refused to process the request because the request does not specify the length of its content.
412 | Precondition Failed | The server does not meet one of the preconditions that the requester puts on the request.
413 | Request Entity Too Large | The server refuses to process a request because the request entity is too large. The server may disable the connection to prevent the client from sending requests consecutively. If the server temporarily cannot process the request, the response will contain a Retry-After header field.
414 | Request-URI Too Large | The URI provided was too long for the server to process.
415 | Unsupported Media Type | The server does not support the media type in the request.
416 | Requested range not satisfiable | The requested range is invalid.
417 | Expectation Failed | The server fails to meet the requirements of the Expect request-header field.
422 | UnprocessableEntity | The request is well-formed but is unable to be processed due to semantic errors.
429 | TooManyRequests | The client sends excessive requests to the server within a given time (exceeding the limit on the access frequency of the client), or the server receives excessive requests within a given time (beyond its processing capability). In this case, the client should repeat requests after the time specified in the Retry-After header of the response expires.
500 | InternalServerError | The server is able to receive the request but it could not understand the request.
501 | Not Implemented | The server does not support the requested function.
502 | Bad Gateway | The server acting as a gateway or proxy receives an invalid response from a remote server.
503 | ServiceUnavailable | The requested service is invalid. The client should modify the request instead of re-initiating it.
504 | ServerTimeout | The server could not return a timely response. The response will reach the client only if the request carries a timeout parameter.
505 | HTTP Version not supported | The server does not support the HTTP protocol version used in the request.

Parent topic: Appendix