Status Codes
Table 1 describes status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The client should continue sending its request. This interim response is used to inform the client that part of the request has been received and has not yet been rejected by the server. |
101 |
Switching Protocols |
The server is switching to a new protocol. The protocol can only be switched to a more advanced one. For example, the protocol in use is switched to a later version of HTTP. |
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 |
Unauthorized information. The request is successful. |
204 |
NoContent |
The server has successfully processed the request, but does not return any response. 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 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 |
This and all future requests have been permanently moved to the given URI indicated in this response. |
302 |
Found |
The requested resource has been temporarily moved. |
303 |
See Other |
The server is redirecting the client to a different address. The response to the request 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 is available only 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 |
The authentication information provided by the client is incorrect or invalid. |
402 |
Payment Required |
Reserved request. |
403 |
Forbidden |
The request has been rejected. The client should modify the request instead of re-initiating it. |
404 |
NotFound |
The requested resource cannot 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 cannot fulfill 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 server timed out waiting for the request. The client may repeat the request without modifications at a later time. |
409 |
Conflict |
The request could not be processed due to a conflict with the current state of the resource. The resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request. |
410 |
Gone |
The requested resource cannot be found. The requested resource has been deleted permanently. |
411 |
Length Required |
The server refused to process the request because the request does not specify the length of its content. |
412 |
Precondition Failed |
The server did not meet one of the preconditions contained in the request. |
413 |
Request Entity Too Large |
The server refused the request because the request was too large. The server may disable the connection to prevent the client from sending requests consecutively. If the server is only temporarily unable to 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 be processed due to semantic errors. |
429 |
TooManyRequests |
The client has sent more requests than the rate limit allowed within a given amount of time, or the server has received more requests than it is able to process within a given amount of time. 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 is able to receive the request but unable to understand it. |
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 unavailable. The client should not repeat the request without modifications. |
504 |
ServerTimeout |
The request cannot be fulfilled within a given amount of 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