ListMultipartUploads

Article summary

Did you find this summary helpful?

Thank you for your feedback

Available in Classic and VPC

View canceled or incomplete multipart upload information. No request body is used for the operation.

Requests

The following describes the request format for the endpoint. The request format is as follows.

Method	URI
GET	/{bucket-name}

Request syntax

The request syntax is as follows.

GET https://{endpoint}/{bucket-name}?uploads= # path style
GET https://{bucket-name}.{endpoint}?uploads= # virtual host style

Request headers

For headers common to all Object Storage APIs, see Object Storage common request headers.

Request path parameters

The following describes the parameters.

Field	Type	Required	Description
`bucket-name`	String	Required	Name of the bucket to view multipart upload information for

Request query parameters

The following describes the parameters.

Field	Type	Required	Description
`uploads`	String	Required	Declare multipart upload information retrieval Enter only keys without values
`prefix`	String	Optional	Prefix to limit responses Limit the response to object names starting with the prefix
`delimiter`	String	Optional	Criteria for binding objects Bind the objects between the prefix and delimiter together
`encoding-type`	String	Optional	Encoding type Resolve encoding issues by setting the parameter to URL if Unicode characters not supported by XML are used in the object name
`max-uploads`	Integer	Optional	Number of objects to display in the response 0 - 1000 (default: 1000)
`key-marker`	String	Optional	List start point Specify objects starting at the `key-marker` position
`upload-id-marker`	String	Conditional	List start point Required if `key-marker` is specified

Request example

The following is a sample request.

GET /apiary?uploads= HTTP/1.1
Authorization: {authorization-string}
x-amz-date: 20161011T190354Z
Host: kr.object.ncloudstorage.com

Responses

The following describes the response format.

Response headers

For response headers common to all Object Storage APIs, see Object Storage common response headers.

Response status codes

For response status codes common to all Object Storage APIs, see Object Storage response status codes.

Response example

The following is a sample response.

HTTP/1.1 200 OK
Date: Wed, 5 Oct 2016 15:22:27 GMT
Accept-Ranges: bytes
x-amz-request-id: 9fa96daa-9f37-42ee-ab79-0bcda049c671
Content-Type: application/xml
Content-Length: 374

<ListMultipartUploadsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
  <Bucket>apiary</Bucket>
  <KeyMarker/>
  <UploadIdMarker/>
  <NextKeyMarker>multipart-object-123</NextKeyMarker>
  <NextUploadIdMarker>0000015a-df89-51d0-2790-dee1ac994053</NextUploadIdMarker>
  <MaxUploads>1000</MaxUploads>
  <IsTruncated>false</IsTruncated>
  <Upload>
    <Key>file</Key>
    <UploadId>0000015a-d92a-bc4a-c312-8c1c2a0e89db</UploadId>
    <Initiator>
      <ID>d4d11b981e6e489486a945d640d41c4d</ID>
      <DisplayName>d4d11b981e6e489486a945d640d41c4d</DisplayName>
    </Initiator>
    <Owner>
      <ID>d4d11b981e6e489486a945d640d41c4d</ID>
      <DisplayName>d4d11b981e6e489486a945d640d41c4d</DisplayName>
    </Owner>
    <StorageClass>STANDARD</StorageClass>
    <Initiated>2017-03-16T22:09:01.002Z</Initiated>
  </Upload>
  <Upload>
    <Key>multipart-object-123</Key>
    <UploadId>0000015a-df89-51d0-2790-dee1ac994053</UploadId>
    <Initiator>
      <ID>d4d11b981e6e489486a945d640d41c4d</ID>
      <DisplayName>d4d11b981e6e489486a945d640d41c4d</DisplayName>
    </Initiator>
    <Owner>
      <ID>d4d11b981e6e489486a945d640d41c4d</ID>
      <DisplayName>d4d11b981e6e489486a945d640d41c4d</DisplayName>
    </Owner>
    <StorageClass>STANDARD</StorageClass>
    <Initiated>2017-03-18T03:50:02.960Z</Initiated>
  </Upload>
</ListMultipartUploadsResult>

Was this article helpful?

What's Next

PutObject

Table of contents

Requests
Responses