Status Code
Table 1 describes status codes.
Status Code |
Code |
Description |
---|---|---|
100 |
Continue |
The client should continue with its request. This interim response is used to inform the client that some requests have been received and have not been rejected by the server. |
101 |
Switching Protocols |
The protocol should be switched. The protocol can only be switched to a newer protocol. For example, the current HTTP protocol is switched to a later version. |
201 |
Created |
The request for creating resources has been fulfilled. |
202 |
Accepted |
The request has been accepted, but the processing has not been completed. |
203 |
Non-Authoritative Information |
Non-authoritative information. The request is successful. |
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 requester is required to reset the content. |
206 |
Partial Content |
The server has successfully processed the partial 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 with a new permanent URI. This 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, 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 |
This HTTP status code is no longer used. |
400 |
BadRequest |
The request is invalid. The client should not repeat the request without modifications. |
401 |
Unauthorized |
This 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 |
Access denied. The server understands the request, but refuses to fulfill it. The client should not repeat the request without modifications. |
404 |
NotFound |
The requested resource cannot be found. The client should not repeat the request without modifications. |
405 |
MethodNotAllowed |
The method specified in the request is not supported by the requested resource. The client should not repeat the request without modifications. |
406 |
Not Acceptable |
The server cannot fulfill the request based on the content characteristics of the request. |
407 |
Proxy Authentication Required |
This status code is similar to 401, but indicates that the client must authenticate itself with the proxy first. |
408 |
Request Time-out |
The client does not send a request within the time that the server was prepared to wait. The client may repeat the request without modifications later. |
409 |
Conflict |
The request cannot be processed due to a conflict. 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 cannot be found. 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 server refuses to process a request because the request entity is too large. The server may disable the connection to prevent the client from sending requests consecutively. If the server cannot process the request temporarily, the response will contain a Retry-After 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 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 |
InternalServerError |
The server is able to receive the request 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 acting as a gateway or proxy receives an invalid response from a remote server. |
503 |
ServiceUnavailable |
The requested service is invalid. The client should not repeat the request without modifications. |
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