The table below describes HTTP status codes that can be returned in response to a request to store an object. For more information on HTTP status codes and the error codes that can accompany them, see Error codes.
Code | Meaning | Description |
---|---|---|
200 | OK |
HCP successfully stored the object. |
400 | Bad Request |
One of: •An ACL grant header specifies an invalid grantee. •The value specified by the Content-MD5 header does not match the Base64-encoded MD5 hash of the data HCP received. |
403 | Forbidden |
One of: •The credentials provided with the request are invalid. •You are not the bucket owner. •The HS3 API is currently disabled for the specified bucket. •The tenant does not currently support use of the HS3 API. |
404 | Not Found | The specified bucket does not exist. |
409 | Conflict |
One of: •An object with the specified name already exists in the specified bucket, and versioning is disabled for that bucket. •A folder with the specified name already exists in the specified bucket. |
413 | Request Entity Too Large | The object you are trying to store is too big for the amount of space left in the bucket. |
500 | Internal Server Error |
An internal error occurred. Try the request again, gradually increasing the delay between each successive attempt. If this error persists, contact your tenant administrator. |
501 | Not Implemented | The request includes the x-amz-acl header with an invalid value. |
503 | Service Unavailable |
HCP is temporarily unable to handle the request, probably due to system overload, maintenance, or upgrade. Try the request again, gradually increasing the delay between each successive attempt. If this error persists, contact your tenant administrator. |
© 2015 Hitachi Data Systems Corporation. All rights reserved.