Status codes for VMware vCloud
The responses obtained from the vCloud API include an HTTP status code and a content type. The only exception is the HTTP status code 204 (No Content), in which the response does not contain a content type.
The response content depends upon the nature of the adapter request. Some responses include a document body, while others include only a URL, and some responses are empty.
The following table provides information about the HTTP status codes returned by the vCloud API:
HTTP status codes
HTTP status code |
Description |
|---|---|
200 OK |
The request is valid and has been executed. The response includes a document body. |
201 Created |
The request is valid. The requested entity has been created and is located at the URL specified in the Location header. |
202 Accepted |
The request is valid and a task has been created to handle it. This response is usually accompanied by a task URL. |
204 No Content |
The request is valid and has been executed. The response includes no document body. |
303 See Other |
The response is located at the URL specified in the Location header. |
400 Bad Request |
The request body is malformed, incomplete, or otherwise invalid. |
401 Unauthorized |
An authorization header was expected but not found. |
403 Forbidden |
The requesting user does not have adequate privileges to access one or more resources specified in the request. |
404 Not Found |
One or more resources specified in the request could not be found in the specified enclosure. |
405 Method Not Allowed |
The HTTP method specified in the request is not supported. |
500 Internal Server Error |
The request was received but could not be executed due to an internal error at the server. |
501 Not Implemented |
The request is not implemented by the server. |
503 Service Unavailable |
One or more services needed to execute the request are not available on the server. |
Comments
Log in or register to comment.