|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
This implementation of the
DELETE operation uses the
policy subresource to delete the policy on a specified bucket. To use
the operation, you must have
DeletePolicy permissions on the
specified bucket and be the bucket owner.
If you do not have
DeletePolicy permissions, Amazon S3 returns a
403 Access Denied error. If you have the correct permissions, but are
not the bucket owner , Amazon S3 returns a
405 Method Not Allowed error. If
the bucket doesn't have a policy, Amazon S3 returns a
204 No Content error.
There are restrictions about who can create bucket policies and which objects in a
bucket they can apply to. For more information, go to Using
DELETE /?policy HTTP/1.1 Host:
This implementation of the operation does not use request parameters.
This implementation of the operation uses only request headers that are common to all operations. For more information, see Common Request Headers.
This implementation of the operation does not use request elements.
This implementation of the operation uses only response headers that are common to most responses. For more information, see Common Response Headers.
The response elements contain the status of the
operation including the error code if the request failed.
This implementation of the operation does not return special errors. For general information about Amazon S3 errors and a list of error codes, see Error Responses.
This request deletes the bucket named
DELETE /?policy HTTP/1.1 Host: BucketName.s3.amazonaws.com Date: Tue, 04 Apr 2010 20:34:56 GMT Authorization: AWS AKIAIOSFODNN7EXAMPLE:k3nL7gH3+PadhTEVn5EXAMPLE
HTTP/1.1 204 No Content x-amz-id-2: Uuag1LuByRx9e6j5OnimrSAMPLEtRPfTaOFg== x-amz-request-id: 656c76696e672SAMPLE5657374 Date: Tue, 04 Apr 2010 20:34:56 GMT Connection: keep-alive Server: AmazonS3