Status Codes
Status Code |
Code |
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 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 HTTPS protocol is switched to a later version. |
200 |
OK |
The server has successfully processed the request. |
201 |
Created |
The request for creating a resource has been fulfilled. |
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 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 is required to 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 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 |
Retrieve a location. 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. 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 |
The HTTP status code is no longer used. |
400 |
Bad Request |
The request is invalid. The client should not repeat the request without modifications. |
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 server understood the request, but is refusing to fulfill 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 method specified in the request is not supported for the requested resource. The client should not repeat the request without modifications. |
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 indicates that the client must first authenticate itself with the proxy. |
408 |
Request Timeout |
The server times out when waiting for the request. The client may repeat the request without modifications at any later time. |
409 |
Conflict |
The request could not be completed due to a conflict with the current state of the resource. 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 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 that a server is 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 fails to 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 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 |
Internal Server Error |
The server is able to receive but unable to understand the request. |
501 |
Not Implemented |
The server does not support the function required to fulfill the request. |
502 |
Bad Gateway |
The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
503 |
Service Unavailable |
The requested service is invalid. The client should not repeat the request without modifications. |
504 |
Gateway Timeout |
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 HTTPS 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