HCP Tenant Management Help


HTTP status codes (PUT bucket versioning)

The table below describes HTTP status codes that can be returned in response to a request to enable or disable versioning for 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 enabled or disabled versioning for the bucket.

400 Bad Request Possible reasons include that the XML in the versioning request body is malformed or contains an invalid value.
403 Forbidden

Possible reasons include:

The credentials provided with the request are invalid.

You are not the bucket owner.

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

The tenant does not currently support use of the S3 compatible API for enabling or disabling bucket versioning.

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.