Status Codes
The following table describes the status codes.
Status Code | Code | Status Code Description |
|---|---|---|
100 | Continue | The client should proceed with the request. This temporary response is used to inform the client that some requests have been received and not rejected by the server. |
101 | Switching Protocols | The protocol should be switched. The protocol can only be switched to a later version. For example, switch the current HTTP protocol to the latest version. |
200 | OK | The request has been fulfilled. |
201 | Created | The request for creating a resource has been fulfilled. |
202 | Accepted | The request has been accepted but is still being processed. |
203 | Non-Authoritative Information | Non-authoritative information. The request is successful. |
204 | NoContent | The request has been fulfilled, but the HTTP response does not contain a response body. The status code is returned in response to an HTTP OPTIONS request. |
205 | Reset Content | The server has fulfilled the request, but the client is required to reset the content. |
206 | Partial Content | The server has 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 the user or user agent (such as a browser) can choose the most appropriate one. |
301 | Moved Permanently | The requested resource has been assigned a new permanent URI, and the 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 HTTP status code is no longer used. |
400 | BadRequest | The request is invalid. Modify the request and then try again. |
401 | Unauthorized | This status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid. |
402 | Payment Required | This request is reserved. |
403 | Forbidden | The request has been rejected. The server has received and understood the request; yet it refused to respond, because the request is set to deny access. Do not retry the request before modification. |
404 | NotFound | The requested resource cannot be found. Modify the request and then try again. |
405 | MethodNotAllowed | The request contains one or more methods not supported for the resource. Modify the request and then try again. |
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 request timed out. 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 requested update failed due to 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 requirements that the requester puts on the request. |
413 | Request Entity Too Large | The request is larger than that a server can process. The server may disconnect the connection to prevent the client from continuously sending the request. If the server cannot process the request temporarily, 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 media format in the request is not supported. |
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 process 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 retry after the time period specified in the Retry-After response header. |
500 | InternalServerError | The server is able to receive but unable to 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 has received an invalid request from a remote server. |
503 | ServiceUnavailable | The requested service is invalid. Modify the request and then try again. |
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
