Status Codes
Table 1 describes status codes.
| Status Code | Message | Description |
|---|---|---|
| 100 | Continue | The client should continue with the request. This interim response is used to inform the client that part of its request has been received and has not been rejected by the server. |
| 101 | Switching Protocols | The protocol should be switched. The protocol can only be switched to a more advanced protocol. For example, switch to a new HTTP protocol. |
| 200 | OK | The request has succeeded. |
| 201 | Created | The request has been fulfilled and resulted in a new resource being created. |
| 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 | No Content | The server has successfully processed the request, but did not return 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 has to reset the content. |
| 206 | Partial Content | The server has fulfilled the partial GET request for the resource. |
| 300 | Multiple Choices | There are multiple options for the location of the requested resources. The response contains a list of resource characteristics and addresses from which the user or user agent (such as a browser) can choose the most appropriate one. |
| 301 | Moved Permanently | This and all future requests have been permanently moved to the given URI indicated in this 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. When the server returns this status code, it does not return any resources. |
| 305 | Use Proxy | The requested resource must be accessed through a proxy. |
| 306 | Unused | This HTTP status code has been deprecated. |
| 400 | Bad Request | The request is invalid. The client should not repeat the request without modifications. |
| 401 | Unauthorized | The client's request lacks valid authentication credentials. |
| 402 | Payment Required | Reserved for future use. |
| 403 | Forbidden | The request has been rejected. The server has received the request and understood it, but the server refuses to respond to it. The client should not repeat the request without modifications. |
| 404 | Not Found | The requested resource cannot be found. The client should not repeat the request without modifications. |
| 405 | Method Not Allowed | The request contains one or more methods not supported for the resource. The client should not repeat the request without modifications. |
| 406 | Not Acceptable | The server cannot produce a response matching the list of acceptable values. |
| 407 | Proxy Authentication Required | The request requires proxy authentication. This status code is similar to 401, but the client must authenticate itself with the proxy. |
| 408 | Request Timeout | The server timed out waiting for the request. The client may re-initiate the request without modifications at any time later. |
| 409 | Conflict | The request could not be processed due to a conflict. The resource that the client attempts to create already exists, or the request fails to be processed because of a conflict. |
| 410 | Gone | The requested resource is no longer available. The target resource has been permanently deleted. |
| 411 | Length Required | The server refuses to process the request without a defined Content-Length. |
| 412 | Precondition Failed | The server did not meet one of the preconditions that the requester put on the request. |
| 413 | Request Entity Too Large | The request is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request. If the server cannot process the request temporarily, the response will contain a Retry-After header field. |
| 414 | Request-URI Too Long | The URI provided was too long for the server to process. |
| 415 | Unsupported Media Type | The server is unable to process the media format in the request. |
| 416 | Requested Range Not Satisfiable | The requested range is invalid. |
| 417 | Expectation Failed | The server cannot meet the requirements of the Expect request-header field. |
| 422 | Unprocessable Entity | The request is well-formed but is unable to be processed due to semantic errors. |
| 429 | Too Many Requests | The client has sent more requests than its rate limit is allowed within a given amount of time, or the server has received more requests than it is able to process within a given amount of time. In this case, it is advisable for the client to re-initiate requests after the time specified in the Retry-After header of the response expires. |
| 500 | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | The server does not support the requested function. |
| 502 | Bad Gateway | The server is acting as a gateway or proxy and receives an invalid request from a remote server. |
| 503 | Service Unavailable | The requested service is invalid. The client should not repeat the request without modifications. |
| 504 | Server Timeout | The request cannot be fulfilled within a given time. 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 and cannot complete the processing. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot