UploadPart
Last update：2022-03-01 18:22:19
-
After a multi-part upload task is created, the user can upload new data from the client by specifying the number of the multi-part upload task, uploading parts for a specific task through the upload part interface. When uploading parts of the same multipart upload task for the same object, the upload sequence has no effect on the subsequent merge operation, that is, it supports concurrent upload of multiple parts.
-
The number of the upload segment has a range limitation, and the range is [1,10000]. The segment number is the only way to determine a segment and its position when it is merged. If a segment with a duplicate segment number is uploaded, the previously uploaded segment with the same number will be overwritten. The minimum segment size is 5MB, but there is no limit to the size of the last segment when merging segments.
-
In order to ensure that the data is not damaged during the transmission process, you can add the Content-MD5 request header, and the system will check the MD5. If the MD5 is incorrect, WOS will give an error message.
Note: If a multi-segment task is created and one or more segments have been uploaded, the occupied storage space will only be released after the segments are merged or the multi-segment task is cancelled, otherwise the occupied space will not be released.
Request syntax
PUT /ObjectName?partNumber=partNum&uploadId=uploadId HTTP/1.1
Host: Bucket.Endpoint
Date: date
Content-Length: Size
Authorization: authorization
Content-MD5：md5
URI request parameters
parameter name | description | Is it required |
partNumber | The number of the upload segment, the range is [1,10000] | Yes |
uploadId | Initiate Multipart Upload response upload id | Yes |
Request header
Only use public request headers .
Request body
Sharded data
Response syntax
HTTP/1.1 status_code
x-wos-request-id: request id
Date: date
ETag: etagValue
Content-Length: length
Server: : WS-web-server
Response header
Only use public response headers .
Response element
no
Special error
Situation | Http Status | Error Code | Message |
There is only one parameter in the signature and URL , uploadId or partNumber | 400 Bad Request | InvalidArgument | Invalid Argument |
UploadId/partNumber is carried in the signature and URL , and the order is the same, but the order is not normal | 400 Bad Request | InvalidArgument | Invalid Argument |
partNumer>10000 | 400 Bad Request | InvalidArgument | Part number must be an integer between 1 and 10000 |
The partsize of a single upload >=5G | 400 Bad Request | EntityTooLarge | Your proposed upload exceeds the maximum allowed object size. |
Example
PUT /ObjectName?partNumber=1&uploadId=VCVsb2FkIElEIGZvciBlbZZpbmcncyBteS1tb3ZpZS5tMnRzIHVwbG9hZR HTTP/1.1
Host: bucket.s3-cn-east-1.wcsapi.com
Date: Mon, 1 Nov 2010 20:34:56 GMT
Content-Length: 1048596
Authorization:WOS 14RZT432N80TGDF2Y2G2:8se2hm3YLchJhuPMDrybeITcuo0=
Content-MD5:q3q7DaS8pTI6thGbtdzSlg==
HTTP/1.1 200 OK
x-wos-request-id: 656c76696e6727732072657175657374
Date: Mon, 1 Nov 2010 20:34:56 GMT
ETag: "b54357faf0632cce46e942fa68356b38"
Content-Length: 1048596
Server：WCS-web-server