PUT Bucket Versioning

The PUT Bucket Versioning operation enables the bucket owner to set the versioning state of an existing bucket. Supported versioning state values are as follows:

• Enabled - Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.

• Disabled - Disables versioning for the objects in the bucket. All objects added to the bucket receive the version ID null.

Note:

If the versioning state has never been set on a bucket, it has no versioning state; a GET versioning request does not return a versioning state value.

Syntax Example

PUT https://appliance:443/s3/v1/export/share_mount_point_path/bucketname?versioning

Request Parameters

This implementation of the PUT Bucket Versioning operation does not support the use of request parameters.

Request Headers

The PUT Bucket Versioning operation uses only request headers that are common to all operations. For more information, see table "Common Supported Request Headers" in Supported Common Request Headers.

Request Elements

The PUT Bucket Versioning operation supports the use of the Status and VersioningConfiguration request elements. For more information about these request elements, see PUT Bucket versioning.

Response Headers

The PUT Bucket Versioning operation uses only response headers that are common to most responses. For more information, see table "Supported Response Headers" in Supported Common Response Headers.

Response Elements

This implementation of the PUT Bucket Versioning operation does not return response elements.

Expected HTTP Response Code

200 OK

Error Response Code

The PUT Bucket Versioning operation does not return special errors. For general information about S3 errors and a list of error codes, see S3 Client Error Handling Reference.

Example

PUT /?versioning
<VersioningConfiguration> 
  <Status>Enabled</Status> 
</VersioningConfiguration>
HTTP/1.1 200 OK