Querying Multipart Upload

Last Updated At: 2025-10-21 09:10:00

Description

List Multipart Uploads is used to query the parts being uploaded. A maximum of 1,000 parts being uploaded can be listed in a single request at a time.

Note:

Read permissions for the bucket are required for this request.

Request

Request Example

GET /?uploads HTTP/1.1
Host: <BucketName-APPID>.<Endpoint>
Date: GMT Date
Authorization: Auth String

Note:

Authorization: Auth String (For details, please refer to the Request Signature document).

Request Header

Common Headers

This request uses common request headers. For details, see Common Request Headers.

Non-common Headers

This request has no special request header information.

Request Parameters

The specific contents are as follows:

Name Description Type Required
delimiter The delimiter is a symbol. Objects whose names contain the specified prefix and the first occurrence of the delimiter character are considered as a group of elements: common prefix. If there is no prefix, it starts from the beginning of the path. String No
encoding-type Specifies the encoding format of the return value. Legal value: url String No
prefix The returned Object key must be prefixed with Prefix.
Note that if you use this parameter, the returned keys will contain this prefix.
String No
max-uploads Set the maximum number of multiparts returned. The legal value is from 1 to 1000. The default value is 1000. String No
key-marker Used together with upload-id-marker
When upload-id-marker is not specified, entries with ObjectNames alphabetically greater than key-marker will be listed.
When upload-id-marker is specified, entries with an ObjectName alphabetically greater than key-marker are listed, and entries with an ObjectName alphabetically equal to key-marker and an UploadID greater than upload-id-marker are listed.
String No
upload-id-marker Used with key-marker
When key-marker is not specified, upload-id-marker will be ignored.
When key-marker is specified, entries with an ObjectName greater than key-marker in alphabetical order are listed, and entries with an ObjectName equal to key-marker in alphabetical order and an UploadID greater than upload-id-marker are listed.
String No

Request Body

The request body of this request is empty.

Response

Response Headers

Common Response Headers

This response contains common response headers. For details on common response headers, please refer to the Common Response Header document.

Special Response Headers

There are no special response headers for this response operation.

Response Body

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

<ListMultipartUploadsResult>
  <Bucket></Bucket>
  <Encoding-Type></Encoding-Type>
  <KeyMarker></KeyMarker>
  <UploadIdMarker></UploadIdMarker>
  <NextKeyMarker></NextKeyMarker>
  <NextUploadIdMarker></NextUploadIdMarker>
  <MaxUploads></MaxUploads>
  <IsTruncated></IsTruncated>
  <Prefix></Prefix>
  <Delimiter></Delimiter>
  <Upload>
    <Key></Key>
    <UploadID></UploadID>
    <StorageClass></StorageClass>
    <Initiator>
      <ID></ID>
    <DisplayName></DisplayName>
    </Initiator>
    <Owner>
      <ID></ID>
    <DisplayName></DisplayName>
    </Owner>
    <Initiated></Initiated>
  </Upload>
  <CommonPrefixes>
    <Prefix></Prefix>
  </CommonPrefixes>
</ListMultipartUploadsResult>

The data are as follows:

Node Name (Keyword) Parent Node Description Type
ListMultipartUploadsResult No Used to describe all the information about the multipart upload Container

Contents of the Container node ListMultipartUploadsResult:

Node Name (Keyword) Parent Node Description Type
Bucket ListMultipartUploadsResult Target Bucket for multipart upload, consisting of a user-defined string and a system-generated APPID digit string connected by a hyphen, for example: examplebucket-1250000000 String
Encoding-Type ListMultipartUploadsResult Specifies the encoding format of the return value. Legal value: url String
KeyMarker ListMultipartUploadsResult List entries starting from this key value String
UploadIdMarker ListMultipartUploadsResult List entries starting with this UploadId value String
NextKeyMarker ListMultipartUploadsResult If the returned entry is truncated, the returned NextKeyMarker is the starting point of the next entry. String
NextUploadIdMarker ListMultipartUploadsResult If the returned entry is truncated, the returned UploadId is the starting point of the next entry. String
MaxUploads ListMultipartUploadsResult Set the maximum number of multiparts returned. The legal value is from 0 to 1000. String
IsTruncated ListMultipartUploadsResult Returns whether the entry is truncated. Boolean value is TRUE or FALSE. Boolean
Prefix ListMultipartUploadsResult A prefix that the returned object keys must start with.
Note that if you use this parameter, the returned keys will contain this prefix.
String
Delimiter ListMultipartUploadsResult The delimiter is a symbol. The objects whose names contain the specified prefix and the first occurrence of the delimiter character are regarded as a group of elements: common prefix. If there is no prefix, it starts from the beginning of the path. String
Upload ListMultipartUploadsResult Information about each upload Container
CommonPrefixes ListMultipartUploadsResult Group the same paths from prefix to delimiter into one category and define it as Common Prefix Container

Contents of the Container node upload:

Node Name (Keyword) Parent Node Description Type
Key ListMultipartUploadsResult.Upload Name of an object. String
UploadID ListMultipartUploadsResult.Upload ID of the multipart upload String
StorageClass ListMultipartUploadsResult.Upload Used to indicate the storage level of parts, enumeration value: STANDARD, STANDARD_IA, and ARCHIVE String
Initiator ListMultipartUploadsResult.Upload Used to indicate the information of the initiator of this upload Container
Owner ListMultipartUploadsResult.Upload Used to indicate the information of the owners of these parts Container
Initiated ListMultipartUploadsResult.Upload Start time of multipart upload. Date

Contents of the Container node Initiator:

Node Name (Keyword) Parent Node Description Type
ID ListMultipartUploadsResult.Upload.Initiator User's unique CAM ID String
DisplayName ListMultipartUploadsResult.Upload.Initiator Abbreviation for User Identity Number (UIN) String

Content of Owner:

Node Name (Keyword) Parent Node Description Type
ID ListMultipartUploadsResult.Upload.Owner User's unique CAM ID String
DisplayName ListMultipartUploadsResult.Upload.Owner Abbreviation for User Identity Number (UIN) String

Contents of the Container node CommonPrefixes:

Node Name (Keyword) Parent Node Description Type
Prefix ListMultipartUploadsResult.CommonPrefixes Display specific CommonPrefixes String

Error Analysis

The following describes some special but common errors that may occur with this request:

Error Code HTTP Status Code Description
InvalidArgument 400 Bad Request max-uploads must be an integer between 0 and 1000, otherwise InvalidArgument is returned.
encoding-type can only be set to url; otherwise, InvalidArgument will be returned.

For more information on COS error codes or the complete list of product errors, please refer to the Error Codes document.

Practical Case

Request

GET /?uploads HTTP/1.1
Host: examplebucket-1250000000.cos.city.yfm4.fsphere.cn
Date: Wed, 18 Jan 2015 21:32:00 GMT
Authorization: q-sign-algorithm=sha1&q-ak=AKIDxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&q-sign-time=1484727508;32557623508&q-key-time=1484727508;32557623508&q-header-list=host&q-url-param-list=uploads&q-signature=5bd4759a7309f7da9a0550c224d8c61589c9dbbf

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 1203
Date: Wed, 18 Jan 2015 21:32:00 GMT
x-cos-request-id: NTg3ZjI0ZGRfNDQyMDRlXzNhZmRfMjRl

<ListMultipartUploadsResult>
    <Bucket>examplebucket-1250000000</Bucket>
    <Encoding-Type/>
    <KeyMarker/>
    <UploadIdMarker/>
    <MaxUploads>1000</MaxUploads>
    <Prefix/>
    <Delimiter>/</Delimiter>
    <IsTruncated>false</IsTruncated>
    <Upload>
        <Key>Object</Key>
        <UploadID>1484726657932bcb5b17f7a98a8cad9fc36a340ff204c79bd2f51e7dddf0b6d1da6220520c</UploadID>
        <Initiator>
           <ID>qcs::cam::uin/100000000001:uin/100000000001</ID>
        <DisplayName>100000000001</DisplayName>
        </Initiator>
        <Owner>
           <ID>qcs::cam::uin/100000000001:uin/100000000001</ID>
        <DisplayName>100000000001</DisplayName>
        </Owner>
        <StorageClass>Standard</StorageClass>
        <Initiated>Wed Jan 18 16:04:17 2017</Initiated>
    </Upload>
    <Upload>
        <Key>Object</Key>
        <UploadID>1484727158f2b8034e5407d18cbf28e84f754b791ecab607d25a2e52de9fee641e5f60707c</UploadID>
        <Initiator>
           <ID>qcs::cam::uin/100000000001:uin/100000000001</ID>
        <DisplayName>100000000001</DisplayName>
        </Initiator>
        <Owner>
           <ID>qcs::cam::uin/100000000001:uin/100000000001</ID>
        <DisplayName>100000000001</DisplayName>
        </Owner>
        <StorageClass>Standard</StorageClass>
        <Initiated>Wed Jan 18 16:12:38 2017</Initiated>
    </Upload>
    <Upload>
        <Key>exampleobject</Key>
        <UploadID>1484727270323ddb949d528c629235314a9ead80f0ba5d993a3d76b460e6a9cceb9633b08e</UploadID>
        <Initiator>
           <ID>qcs::cam::uin/100000000001:uin/100000000001</ID>
        <DisplayName>100000000001</DisplayName>
        </Initiator>
        <Owner>
           <ID>qcs::cam::uin/100000000001:uin/100000000001</ID>
        <DisplayName>100000000001</DisplayName>
        </Owner>
        <StorageClass>Standard</StorageClass>
        <Initiated>Wed Jan 18 16:14:30 2017</Initiated>
    </Upload>
</ListMultipartUploadsResult>