Status Codes
Status Code |
Description |
---|---|
200 OK |
The request is normal. |
201 Created |
The request has been fulfilled and resulted in a new resource being created. |
202 Accepted |
The request has been accepted, but the processing has not been completed. |
204 No Content |
The server successfully processed the request and is not returning any content. |
400 Bad Request |
The request could not be understood by the server due to malformed syntax. The client should modify the request instead of re-initiating it. |
401 Unauthorized |
The authentication information is incorrect or invalid. |
403 Forbidden |
The server understood the request, but is refusing to fulfill it. The client should not repeat the request without modifications. |
404 Not Found |
The requested resource cannot be found. The client should modify the request instead of re-initiating it. |
405 Method Not Allowed |
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 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 Timeout |
The client does not produce a request within the time that the server was prepared to wait. The client may repeat the request without modifications at any later time. |
409 Conflict |
The request could not be completed due to a conflict with the current state of the resource. This status code indicates 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 is no longer available. The status code indicates that the requested resource has been deleted permanently. |
429 Too Many Request |
The client has sent more requests than its rate limit is 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 repeat requests after the time specified in the Retry-After header of the response expires. |
500 Internal Server Error |
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, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
503 Service Unavailable |
The requested service is unavailable. The client should modify the request instead of re-initiating it. |
504 Gateway Timeout |
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. |
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