This API is used to delete the cross-bucket replication configuration from a bucket. When initiating this request, you need to get the request signature to show that the request has been authorized.
DELETE /?replication HTTP/1.1 Host: <BucketName-APPID>.cos.<Region>.myqcloud.com Date: GMT Date Authorization: Auth String
Authorization: Auth String (See Request Signature for details.)
This API only uses common request headers. For more information, please see Common Request Headers.
The request body of this request is empty.
This API returns only common response headers. For more information, please see Common Response Headers.
The response body is empty.
This API returns common error responses and error codes. For more information, please see Error Codes.
The following sample request deletes the configuration of the
DELETE /?replication HTTP/1.1 Date: Fri, 14 Apr 2019 07:47:35 GMT Authorization: q-sign-algorithm=sha1&q-ak=AKIDZfbOAo7cllgPvF9cXFrJD0a1ICvR****&q-sign-time=1503901499;1503901859&q-key-time=1503901499;1503901859&q-header-list=host&q-url-param-list=replication&q-signature=761f3f6449c6a11684464f4b09c6f292f0a4**** Host: originbucket-1250000000.cos.ap-chengdu.myqcloud.com
After the request above is made, COS returns "204 No Content", which indicates that the cross-bucket replication configuration has been successfully deleted from the bucket. After the configuration is deleted, COS will no longer replicate objects in the source bucket to the destination bucket, and the existing object data in the destination bucket will be retained.
Content-Length: 0 Connection: keep-alive Date: Fri, 14 Apr 2019 07:47:35 GMT Server: tencent-cos x-cos-request-id: NWQwMzUxMTdfMjBiNDU4NjRfNWZlZF84Mjdm**** x-cos-trace-id: OGVmYzZiMmQzYjA2OWNhODk0NTRkMTBiOWVmMDAxODc0OWRkZjk0ZDM1NmI1M2E2MTRlY2MzZDhmNmI5MWI1OWE4OGMxZjNjY2JiNTBmMTVmMWY1MzAzYzkyZGQ2ZWM4MzUyZTg1NGRhNWY0NTJiOGUyNTViYzgyNzgxZTEw****