tencent cloud

Overview

This API is used to copy the parts of an object from the source path to the destination path. You can use x-cos-copy-source to specify the source object and use x-cos-copy-source-range to specify the byte range to copy (each part should be 1 MB to 5 GB).

Note：

• To call this API, you need to first call the Initiate Multipart Upload API to initialize the multipart upload and specify the destination path.
• If the source and destination objects reside in two different regions and the part size is larger than 5 GB, use the multipart upload or multipart copy API to copy the object.
• To upload an object in parts, you must first initialize the multipart upload. The response of the multipart upload initialization will include a unique descriptor uploadId, which needs to be carried in the multipart upload request.

Versioning

If versioning is enabled for the bucket, x-cos-copy-source identifies the current version of the object to copy. If the current version is a delete marker and no version is specified in x-cos-copy-source, COS will consider that the object has been deleted and return a 404 error. If you specify a versionId in x-cos-copy-source and the versionId is a delete marker, COS will return an HTTP 400 error as delete markers cannot be set in x-cos-copy-source.

Requests

Sample request

PUT /examplebucket?partNumber=PartNumber&uploadId=UploadId  HTTP/1.1
Host: <Bucketname-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
x-cos-copy-source: <Bucketname>-<APPID>.cos.<Region>.myqcloud.com/filepath
x-cos-copy-source-range: bytes=first-last
x-cos-copy-source-if-match: etag
x-cos-copy-source-if-none-match : etag
x-cos-copy-source-if-unmodified-since: time_stamp
x-cos-copy-source-if-modified-since: time_stamp

Note：

• In Host: <bucketname-appid>.cos.<region>.myqcloud.com, is the bucket name followed by the APPID, such as examplebucket-1250000000 (see Bucket Overview > Basic Information and Bucket Overview > Bucket Naming Conventions), and is a COS region (see Regions and Access Endpoints).
• Authorization: Auth String (see Request Signature for more information).

Request headers

Common request headers

This API uses common request headers.

Non-common request headers

Required headers

This API uses the following required header:

Recommended headers

This API uses the following recommended headers:

Request parameters

Request body

The request body of this request is empty.

Response

Response headers

Common response headers

This API uses Common Response Headers.

Non-common response headers

Response body

The response body returns application/xml data. The following contains all the nodes:

<?xml version="1.0" encoding="UTF-8" ?>
<CopyPartResult>
 <ETag>"ba82b57cfdfda8bd17ad4e5879ebb4fe"</ETag>
 <LastModified>2017-09-04T04:45:45</LastModified>
</CopyPartResult>

The nodes are described as follows:

Error codes

This API returns common error responses and error codes. For more information, please see Error Codes.

Samples

Request

PUT /exampleobject?partNumber=1&uploadId=1505706248ca8373f8a5cd52cb129f4bcf85e11dc8833df34f4f5bcc456c99c42cd1ffa2f9 HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.1.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
Accept: */*
x-cos-copy-source:examplebucket-1250000000.cos.ap-shanghai.myqcloud.com/exampleobject1
x-cos-copy-source-range: bytes=10-100
Host: examplebucket-1250000000.cos.ap-shanghai.myqcloud.com
Authorization:q-sign-algorithm=sha1&q-ak=AKIDDNMEycgLRPI2axw9xa2Hhx87wZ3M****&q-sign-time=1507530223;1508530223&q-key-time=1507530223;1508530223&q-header-list=&q-url-param-list=&q-signature=d02640c0821c49293e5c289fa07290e6b2f0****

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 133 
Connection: keep-alive 
Date: Mon, 04 Sep 2017 04:45:45 GMT
Server: tencent-cos
x-cos-request-id: NTlkYjFjYWJfMjQ4OGY3MGFfNGIz****
<CopyPartResult>
 <ETag>"ba82b57cfdfda8bd17ad4e5879ebb4fe"</ETag>
 <LastModified>2017-09-04T04:45:45</LastModified>
</CopyPartResult>