Status Codes
The following table describes the status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The client should proceed with 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 |
Switching protocols. The protocol can only be switched to a later version. For example, switch the current HTTP protocol to the latest version. |
200 |
OK |
The request has been fulfilled. |
201 |
Created |
The request for creating a resource has been fulfilled. |
202 |
Accepted |
The request has been accepted but is still being processed. |
203 |
Non-Authoritative Information |
The request has been fulfilled, but the HTTP response does not contain the authoritative information. |
204 |
NoContent |
The request has been fulfilled, but the HTTP response does not contain a response body. The status code is returned in response to an HTTP OPTIONS request. |
205 |
Reset Content |
The server has fulfilled the request, but the client is required to reset the content. |
206 |
Partial Content |
The server has fulfilled the request, but only part of the GET request is processed. |
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 the user or user agent (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. When the server returns this status code, no resource is returned. |
305 |
Use Proxy |
The requested resource must be accessed through a proxy. |
306 |
Unused |
The HTTP status code is no longer used. |
400 |
BadRequest |
The request is invalid. Modify the request and retry. |
401 |
Unauthorized |
The status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid. |
402 |
Payment Required |
This status code is reserved for future use. |
403 |
Forbidden |
The request has been rejected. The server has received and understood the request but it refused to respond, because the request is set to deny access. Modify the request and retry. |
404 |
NotFound |
The requested resource cannot be found. Modify the request and retry. |
405 |
MethodNotAllowed |
The request contains a method that is not supported by the resource. Modify the request and retry. |
406 |
Not Acceptable |
The server cannot 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 be authenticated using a proxy. |
408 |
Request Time-out |
The request timed out. The client may repeat the request without any changes. |
409 |
Conflict |
The request could not be processed due to a conflict with the current state of the resource. This status code indicates that the client attempted to create a resource that already exists, or the requested update failed due to a conflict. |
410 |
Gone |
The requested resource is no longer available. This status code indicates that the requested 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 failed to meet one of the preconditions that the requester puts on the request. |
413 |
Request Entity Too Large |
The server rejects the request because the request entity is too large 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 Large |
The request URI is too long for the server to process. |
415 |
Unsupported Media Type |
The server cannot process the media format 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 has sent 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 acts as a gateway or proxy and receives an invalid request from a remote server. |
503 |
ServiceUnavailable |
The requested service is invalid. Modify the request and retry. |
504 |
ServerTimeout |
The request cannot be fulfilled within a given time. 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