Status Code
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The client should continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. |
101 |
Switching Protocols |
Switch protocols. A protocol can only be switched to a advanced protocol. For example, the protocol in use is switched to a later version of HTTP. |
201 |
Created |
The request has been fulfilled and resulted in a new resource being created. |
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 |
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 fulfilled the partial GET request for the resource. |
300 |
Multiple Choices |
There are multiple choices for a requested resource. A list of resource characteristics and addresses is returned for the client such as a browser to choose from. |
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 |
Retrieve another URL Use GET and POST requests to view the information. |
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 |
Invalid request. The client should modify the request instead of re-initiating it. |
401 |
Unauthorized |
The authentication information provided by the client is incorrect or invalid. |
402 |
Payment Required |
Reserved request. |
403 |
Forbidden |
Request rejected. The server has received the request and understood it, but refuses to respond to it. The client should not repeat the request without modifications. |
404 |
NotFound |
The requested resource cannot be found. The client should modify the request instead of re-initiating it. |
405 |
MethodNotAllowed |
The method specified in the request is not allowed for the requested resource. The client should modify the request instead of re-initiating it. |
406 |
Not Acceptable |
The server cannot implement the request based on 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 re-initiate the request without modifications at any time 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. This status code indicates that 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 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 is too large. The server may disable the connection to prevent the client from sending requests consecutively. If the server temporarily cannot 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 respond due to semantic errors. |
429 |
TooManyRequests |
The client sends too many requests to the server within a given time, exceeding the client's access frequency limit or beyond the server's 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 it cannot understand the request. |
501 |
Not Implemented |
The server does not support the requested function, and therefore cannot implement 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 modify the request instead of re-initiating it. |
504 |
ServerTimeout |
The server could not return a timely response. The response will reach the client only if the request carries a timeout parameter. |
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