Status Code
Table 1 describes status codes.
| Status Code | Message | Description |
|---|---|---|
| 100 | Continue | The client continues sending the request. The server has received the initial part of the request and the client should continue sending the remaining part. |
| 101 | Switching Protocols | The protocol should be switched. 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 and a new resource has been created. |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. |
| 203 | Non-Authoritative Information | This request is successful. |
| 204 | NoContent | The server has successfully processed the request, but has not returned any content. The status code is returned in response to an HTTP OPTIONS request. |
| 205 | Reset Content | The server has fulfilled the request, but the requester must 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 location of the requested resource. The response contains a list of resource characteristics and addresses from which a user terminal (such as a browser) can choose the most appropriate one. |
| 301 | Moved Permanently | The requested resource has been assigned a new permanent URI, and the new URI is contained in the response. |
| 302 | Found | The requested resource resides temporarily under a different URI. |
| 303 | See Other | The response to the request can be found under a different URI. It should be retrieved using a GET or POST method. |
| 304 | Not Modified | The requested resource has not been modified. In this case, there is no need to retransmit the resource since the client still has a previously-downloaded copy. |
| 305 | Use Proxy | The requested resource must be accessed through a proxy. |
| 306 | Unused | The HTTP status code is no longer used. |
| 400 | BadRequest | Invalid request. Do not retry the request before modification. |
| 401 | Unauthorized | This status code is returned after the client provides authentication information to indicate that the information is incorrect or invalid. |
| 402 | Payment Required | This status code is reserved for future use. |
| 403 | Forbidden | The server understands the request, but is refusing to fulfill it. The server has received and understood the request, but it refused to respond, because the request is set to deny access. Do not retry the request before modification. |
| 404 | NotFound | The requested resource cannot be found. Do not retry the request before modification. |
| 405 | MethodNotAllowed | The method specified in the request is not supported by the requested resource. Do not retry the request before modification. |
| 406 | Not Acceptable | The server could not fulfill the request according to the content characteristics of the request. |
| 407 | Proxy Authentication Required | This status code is similar to 401, but the client must first authenticate itself with the proxy. |
| 408 | Request Time-out | The server timed out waiting for the request. The client may repeat the request without modifications at any later time. |
| 409 | Conflict | The request could not be processed due to a conflict in it. This status code indicates that the resource the client is attempting to create already exists, or the requested update failed due to a conflict. |
| 410 | Gone | The requested resource is no longer available. The status code indicates that the requested resource has been deleted permanently. |
| 411 | Length Required | The server refuses to process the request without a defined Content-Length. |
| 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 request is larger than what a server can process. The server may disable the connection to prevent the client from sending consecutive requests. If the server cannot temporarily process the request, the response will contain a Retry-After header field. |
| 414 | Request-URI Too Large | The Request-URI is 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 cannot be processed due to semantic errors. |
| 429 | TooManyRequests | The client has sent an excessive number of requests to the server within a given time (exceeding the limit on the access frequency of the client), or the server has received an excessive number of requests within a given time (beyond its processing capability). In this case, the client should resend the request after the time specified in the Retry-After header of the response has elapsed. |
| 500 | InternalServerError | The server can receive but cannot understand the request. |
| 501 | Not Implemented | The server does not support the requested function. |
| 502 | Bad Gateway | The server was acting as a gateway or proxy and received an invalid request from the remote server. |
| 503 | ServiceUnavailable | The requested service is invalid. Do not retry the request before modification. |
| 504 | ServerTimeout | The request cannot be fulfilled within a given time. This status code is only returned to the client when the Timeout parameter is specified in the request. |
| 505 | HTTP Version not supported | The server does not support the HTTP protocol version used in the request. |
Last Article: Error Codes
Next Article: Obtaining a Project ID
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.