HCP Tenant Management Help


HTTP status codes (PUT bucket ACL)

The table below describes HTTP status codes that can be returned in response to a request to add an ACL to a bucket. 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 added the ACL to the bucket.

400 Bad Request

Possible reasons include:

You are trying to add an ACL that contains more than one hundred permission grants.

A specified grantee does not exist.

The specified owner does not exist.

Two grants of the same permission specify the same grantee.

The x-amz-acl header specifies an invalid value.

An x-amz-grant- header specifies an invalid identifier type.

The XML in the ACL request body is malformed or contains an invalid value.

403 Forbidden

Possible reasons include:

The credentials provided with the request are invalid.

You do not have permission to add an ACL to the bucket.

The specified bucket does not currently support the requested operation.

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

The tenant does not currently support use of the S3 compatible API for adding ACLs to a buckets.

404 Not Found

The specified bucket does not exist.

500 Internal Server Error

An internal error occurred.

If this error persists, contact your tenant administrator.

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, 2019 Hitachi Vantara Corporation. All rights reserved.