Status Codes
Table 1 describes the status codes that may be returned when a MetaStudio API is called.
Status Code |
Description |
---|---|
200 OK |
The request has succeeded. |
201 Created |
The request for creating a resource has been fulfilled. |
202 Accepted |
The request has been accepted for handling, but the handling has not been completed. |
204 No Content |
The request has been fulfilled, but the HTTP response does not contain a response body. |
400 Bad Request |
The request is invalid. Do not retry the request before modifying it. |
401 Unauthorized |
The status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid. |
403 Forbidden |
The request has been rejected. The server has received and understood the request but it refused to respond, because the request is set to deny access. Do not retry the request before modifying it. |
404 Not Found |
The requested resource cannot be found. Do not retry the request before modifying it. |
405 Method Not Allowed |
The request contains one or more methods not allowed for the resource. Do not retry the request before modifying it. |
406 Not Acceptable |
The server cannot fulfill the request sent by the client according to its content characteristics. |
407 Proxy Authentication Required |
This status code is similar to 401, but the client must first authenticate itself with the proxy. |
408 Request Timeout |
The client failed to send a request to the server within the time limit. The client may repeat the request without modifying it at any time later. |
409 Conflict |
The request cannot be handled due to a conflict with the status of the resource. This status code indicates that the resource that the client is attempting to create already exists, or that the requested update cannot be fulfilled due to the conflict. |
500 Internal Server Error |
The server is able to receive but unable to understand the request. |
501 Not Implemented |
The server does not support the requested function. |
502 Bad Gateway |
The server that acts as a gateway or proxy received an invalid request from a remote server. |
503 Service Unavailable |
The requested service is invalid. Do not retry the request before modifying it. |
504 Gateway Timeout |
A gateway timeout error occurred. |
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