Status Codes
Table 1 lists the status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The client should continue with its request. This code is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. |
101 |
Switching Protocols |
The protocol should be switched to a newer protocol. For example, the current HTTPS protocol should be switched to a later version. |
200 |
Success |
The request is successfully sent. |
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 |
The server successfully processed the request, but is returning information that may be from another source. |
204 |
NoContent |
The request has been fulfilled, but the HTTPS response does not contain a response body. The status code is returned in response to an HTTPS 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 a GET request. |
300 |
Multiple Choices |
There are multiple options for 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. 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 |
The HTTPS status code is no longer used. |
400 |
BadRequest |
The request is invalid. The client should not repeat the request without modifications. |
401 |
Unauthorized |
The authorization information provided by the client is incorrect or invalid. |
402 |
Payment Required |
This status code is reserved for future use. |
403 |
Forbidden |
The request is rejected. The server understands the request, but refuses to fulfill it. The client should not repeat the request without modifications. |
404 |
NotFound |
The requested resource could not be found. The client should not repeat the request without modifications. |
405 |
MethodNotAllowed |
A request method is not supported for the requested resource. The client should not repeat the request without modifications. |
406 |
Not Acceptable |
The server could not fulfil 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 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 repeat the request without modifications 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 because of a conflict. |
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 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 was well-formed but was unable to be followed due to semantic errors. |
429 |
TooManyRequests |
The client has sent more requests than its rate limit is allowed within a given time, or the server has received more requests than it is able to process within a given time. 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 requested function. |
502 |
Bad Gateway |
The server was acting as a gateway or proxy and received an invalid request 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 |
HTTPS 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