Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > RightScale API 1.5 > Overview > Error Handling

Error Handling

Table of Contents
No headers

Error handling has been completely revamped in version 1.5 and returns a detailed error message stating exactly why a request failed (i.e. parameter missing errors, resource invalid errors, cloud errors etc.). The response body will include a descriptive error message to assist you with debugging efforts, except in the event of a 500 Internal Server Error.

 HTTP Error Code  Description
 301 Moved Permanently An error code that indicates that the URL has been redirected to another URL. The location for the URL will be listed in the response.
 400 Bad Request Parameter or filter errors, e.g. missing a required parameter. The request should not be repeated without modifying it.
 401 Unauthorized Authentication errors, e.g. wrong username/password or wrong instance token (for instance facing sessions).
 403 Forbidden Authorization errors, e.g. Not having sufficient user 'roles' to perform a particular action or the account might not have the required setting. This error code can also be returned with a "Session cookie is expired or invalid" message indicating that the session has expired.
 404 Not Found Unknown routes, e.g. making a GET request to /api/unknown_route.
 405 Method Not Allowed Method not allowed errors, e.g. making a DELETE request to /api/clouds.
 406 Not Acceptable Unknown format error, e.g. making a GET request to /api/clouds.PDF.
 422 Unprocessable Entity A generic error code that indicates: resource not found (e.g. GET /api/clouds/unknown_cloud), invalid resource (e.g. an error occurred during resource creation), invalid API version (e.g. setting X_API_VERSION to 0.9), or cloud errors (e.g. trying to attach a volume to a device that is already taken).
 500 Internal Server Error Unknown errors, please contact support if you get this error.
504 Gateway Timed Out

The server, while acting as a gateway or proxy, did not receive a
timely response from the upstream server specified by the URI (e.g.
HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed
to access in attempting to complete the request.

Note: To implementors: some deployed proxies are known to
return 400 or 500 when DNS lookups time out.

 

You must to post a comment.
Last modified
23:17, 16 May 2013

Tags

Classifications

This page has no classifications.

Announcements

None


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.