Status Codes

When you call any of the Oracle Application Container Cloud REST resources for caching applications, the Response header returns one of the standard HTTP status codes defined in the following table.

This table describes the HTTP status codes supported in the Oracle Application Container Cloud REST API for caching applications.

HTTP Status Code

Description

200 OK The request was successfully completed. A 200 status is returned for a successful GET or POST method.
204 No Content The request was successfully completed, but no content was returned.
400 Bad Request The path info doesn't have the right format, or a parameter or request body value doesn't have the right format, or a required parameter is missing, or values have the right format but are invalid in some way.
401 Unauthorized The request is not authorized. The authentication credentials included with this request are missing or invalid.
402 Payment Required There is some issue with the account or subscription.
403 Forbidden The user cannot be authenticated. The user does not have authorization to perform this request.
404 Not Found The object referenced by the path does not exist.
406 Not Acceptable The resource identified by this request is not capable of generating a representation corresponding to one of the media types in the Accept header of the request. For example, the client's Accept header requests XML be returned, but the resource can only return JSON.
409 Conflict An attempt was made to create an object that already exists.
500 Internal Server Error The server encountered an unexpected condition that prevented it from fulfilling the request.
503 Service Unavailable The server is unable to handle the request due to temporary overloading or maintenance of the server.