Terminating Multipart Upload

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

Description

Abort Multipart Upload is used to abort multipart upload and delete the uploaded parts. When you call Abort Multipart Upload, if there is a request that is using this Upload Parts to upload parts, an error is returned. When the UploadId does not exist, a 404 NoSuchUpload error will be returned.

Note:

It is recommended to complete multipart uploads promptly or abort multipart uploads because being uploaded but unterminated parts will occupy storage space and incur storage fees.

Request

Request Example

DELETE /<ObjectKey>?uploadId=UploadId 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 documentation).

Request Parameters

The specific contents are as follows:

Parameter Name Description Type Required
uploadId The ID that identifies this multipart upload.
When you use the Initiate Multipart Upload API to initialize multipart upload, you will get an uploadId, which not only uniquely identifies the multipart data, but also identifies the relative position of the multipart data in the entire file.
String Yes

Request Header

Common Headers

The implementation of this request utilizes common request headers. For details on common request headers, please refer to the Common Request Headers documentation.

Non-common Headers

This request has no special request header information.

Request Body

The request body for this request is empty.

Response

Response Headers

Common Response Headers

This response utilizes common response headers. For details on common response headers, please refer to the Common Response Headers documentation.

Special Response Headers

There are no special response headers for this request operation.

Response Body

The response body of this request is empty.

Practical Case

Request

DELETE /exampleobject?uploadId=1484727270323ddb949d528c629235314a9ead80f0ba5d993a3d76b460e6a9cceb9633b08e HTTP/1.1
Host: <BucketName-APPID>.<Endpoint>
Date: Tue, 26 Oct 2013 21:22:00 GMT
Authorization: q-sign-algorithm=sha1&q-ak=AKIDxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&q-sign-time=1484728626;32557624626&q-key-time=1484728626;32557624626&q-header-list=host&q-url-param-list=uploadId&q-signature=2d3036b57cade4a257b48a3a5dc922779a562b18

Response

HTTP/1.1 204 OK
Content-Type: application/xml
Content-Length: 0
Connection: keep-alive
Date: Tue, 26 Oct 2013 21:22:00 GMT
x-cos-request-id: NTg3ZjI5MzlfOTgxZjRlXzZhYjNfMjBh