Available in Classic and VPC
Stop an incomplete upload during a multipart upload and delete the parts. When an upload is stopped, you can no longer upload parts using that upload ID.
Requests
The following describes the request format for the endpoint. The request format is as follows.
| Method | URI |
|---|---|
| DELETE | /{bucket-name}/{object-name} |
Request syntax
The request syntax is as follows.
DELETE https://{endpoint}/{bucket-name}/{object-name}?uploadId={uploadId} # path style
DELETE https://{bucket-name}.{endpoint}/{object-name}?uploadId={uploadId} # virtual host style
Request headers
For headers common to all Object Storage APIs, see Object Storage common headers.
Request path parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
bucket-name |
String | Required | Name of the bucket where the object is stored |
object-name |
String | Required | Name of the object that ran the multipart upload |
Request query parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
uploadId |
String | Required | Upload ID received by running the InitiateMultipartUpload API |
Request example
The following is a sample request.
DELETE /some-bucket/multipart-object-123?uploadId=0000015a-df89-51d0-2790-dee1ac994053 HTTP/1.1
Authorization: {authorization-string}
x-amz-date: 20170318T035641Z
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 204 No Content
Date: Thu, 16 Mar 2017 22:07:48 GMT
Accept-Ranges: bytes