Note:

Only the bucket owner has permission to initiate this request. If the permission policy does not exist, a 204 No Content response is returned.

Request

Request Example

DELETE /?policy HTTP/1.1
Host: <BucketName-APPID>.<Endpoint>
Date: date
Authorization: Auth String

Note:

Authorization: Auth String (See Request Signature for details.)

Request Header

Common Headers

This request operation is implemented by using the public request header. For details about the public request header, see Common Request Headers documentation.

Non-common Headers

This request has no special request header information.

Request Body

The request does not have a request body.

Response

Response Headers

Common Response Headers

This response uses common response headers. For details, see Common Response Headers.

Special Response Headers

There are no special response headers for this response operation.

Response Body

The response body is empty.

Practical Case

Request

DELETE /?policy HTTP/1.1
Host: <BucketName-APPID>.<Endpoint>
Authorization:q-sign-algorithm=sha1&q-ak=AKIDxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&q-sign-time=1484814613;32557710613&q-key-time=1484814613;32557710613&q-header-list=host&q-url-param-list=policy&q-signature=57c9a3f67b786ddabd2c208641944ec7f9b02f98

Response

HTTP/1.1 204 No Content
Content-Type: application/xml
Content-Length: 0
Connection: keep-alive
Date: Thu Jan 19 16:30:21 2017
x-cos-request-id: NTg4MDc5MWRfNDQyMDRlXzNiMDRfZTEw