HTTP status codes (PUT object)

The table below describes HTTP status codes that can be returned in response to a request to store an object. For more information about 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

Possible reasons include:

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

Possible reasons include:

The credentials provided with the request are invalid.

You do not have permission to store objects in the specified bucket.

An object with the specified name already exists in the specified bucket, and versioning is enabled for that bucket, but the existing object is under retention or on hold.

The S3 compatible API is currently disabled for the specified bucket.

404 Not Found The specified bucket does not exist.
409 Conflict

One of these:

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.

411 Length Required Either the request does not include a Content-Length header, or the request includes a Content-Length header with no value.
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.

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, 2020 Hitachi Vantara LLC. All rights reserved.