Status Codes
Table 1 describes the status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
The client should continue with its request. This provisional response informs the client that part of the request has been received and has not yet been rejected by the server. |
101 |
Switching Protocols |
The requester has asked the server to switch protocols and the server is acknowledging that it will do so. The target protocol must be more advanced than the source protocol. For example, the current HTTP protocol is switched to a later version of HTTP. |
200 |
ok |
The server successfully processed the request. |
201 |
Created |
The request was successful and the server created a new resource |
202 |
Accepted |
The server has accepted the request 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 is not returning any content. The status code is returned in response to an HTTP OPTIONS request. |
205 |
Reset Content |
The server has successfully processed the request, but is not returning any content. |
206 |
Partial Content |
The server is delivering only part of the resource due to a range header sent by the client. |
300 |
Multiple Choices |
There are multiple options for the requested resource. 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 resides temporarily under a different URI. |
303 |
See Other |
The response to the request can be found under a different URI, which should be retrieved 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 requester can only access the requested resource using a proxy. |
306 |
Unused |
This HTTP status code is no longer used. |
400 |
BadRequest |
The request cannot be fulfilled due to bad 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 |
This status code is reserved for future use. |
403 |
Forbidden |
The server has received the request and understood it, but the server is refusing to respond to 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 |
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 respond with the content characteristics requested. |
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 later time. |
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 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 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 is refusing 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 server is refusing to process the request because the request URI is longer than that the server is willing to interpret. |
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 cannot 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 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, it is advisable for the client to re-initiate 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 could not understand the request. |
501 |
Not Implemented |
The server does not support the requested function. |
502 |
Bad Gateway |
The server is acting as a gateway or proxy and receives 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 server cannot return a timely response. 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