Status Codes
Table 1 describes status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The client continues sending the request. This temporary response is used to inform the client that some requests have been received and not rejected by the server. |
101 |
Switching Protocols |
Switch protocols. A protocol can only be switched to a more advanced one. For example, the current HTTP protocol is switched to a later version. |
201 |
Created |
The request has been fulfilled and resulted in a new resource being created. |
202 |
Accepted |
The request has been accepted, but has not finished being processed yet. |
203 |
Non-Authoritative Information |
The server successfully processed the request, but is returning information that may be from another source. |
204 |
NoContent |
The request has been successfully implemented, but the HTTP response does not contain a response body. This status code is returned in response to an HTTP OPTIONS request. |
205 |
Reset Content |
The server has fulfilled the request, but the requester is required to reset the content. |
206 |
Partial Content |
The server has successfully processed a part of the GET request. |
300 |
Multiple Choices |
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 |
This and all future requests have been permanently moved 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. The response to the request 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 must be accessed through a proxy. |
306 |
Unused |
This HTTP status code is no longer used. |
400 |
BadRequest |
Invalid request. 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 |
Reserved request. |
403 |
Forbidden |
Request rejected. The server has received the request and understood it, but refuses to respond to it. The client should not repeat the request without modifications. |
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 could not fulfil the request according to 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 client does not produce a request within the time that the server was prepared to wait. The client may re-initiate the request without modifications at any time later. |
409 |
Conflict |
The request cannot be processed due to a conflict. The resource that the client attempts to create already exists, or the update request fails to be processed due to a conflict. |
410 |
Gone |
The requested resource cannot be found. This 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 server refuses to process a request because the request 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 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 is unable to respond due to semantic errors. |
429 |
TooManyRequests |
The client sends too many requests to the server within a given time, exceeding the client's access frequency limit or beyond the server's processing capability. In this case, the client should retry after the time period specified in the Retry-After response header. |
500 |
InternalServerError |
The server is able to receive the request but it cannot understand 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 |
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. This status code is returned to the client only 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. |
Feedback
Was this page helpful?
Provide feedbackThank 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