Status Code
Table 1 describes status codes.
Status Code |
Code |
Error Code Description |
---|---|---|
100 |
Continue |
The client should continue sending the request. This interim response is used to inform the client that the initial part of the requests has been received and not rejected by the server. |
101 |
Switching Protocols |
The requester has asked the server to switch protocols and the server has agreed to do so. The protocol should be switched only when it is advantageous to do so. For example, the protocol in use is switched to a later version of HTTP. |
201 |
Created |
The request has been fulfilled, resulting in the creation of a new resource. |
202 |
Accepted |
The request has been accepted, but the processing has not been completed. |
203 |
Non-Authoritative Information |
The request has been fulfilled. |
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 successfully processed the request, but is not returning any content. |
206 |
Partial Content |
The server has fulfilled the partial GET request for the resource. |
300 |
Multiple Choices |
There are multiple options for the resource from which the client may choose. For example, this code could be used to present a list of resource characteristics and addresses from which the client, such as a browser, may choose. |
301 |
Moved Permanently |
This and all future requests should be permanently directed to the given URI indicated in this response. |
302 |
Found |
The requested resource was temporarily moved. |
303 |
See Other |
The response to the request can be found under another URI using a GET or POST method. |
304 |
Not Modified |
The requested resource has not been modified. In such case, there is no need to retransmit the resource since the client still has a previously downloaded copy. |
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 could not be understood by the server due to malformed syntax. 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 |
Reserved for future use. |
403 |
Forbidden |
The request is rejected. 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 |
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 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 client does not produce a request within the time that the server was prepared to wait. The client may re-initiate the request without any modification at any time. |
409 |
Conflict |
The request could not be completed 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 is no longer available. 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 is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request. If the server temporarily cannot process the request, the response will contain a Retry-After header field. |
414 |
Request-URI Too Large |
The server is refusing to service the request because the request URI is longer than the server is willing to interpret. |
415 |
Unsupported Media Type |
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. |
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 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 encountered an unexpected condition which prevented it from fulfilling the request. |
501 |
Not Implemented |
The server does not support the functionality 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 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