0042-00000220
Updated at:
Problem description
The value of the Content-MD5 header in the CompleteMultipartUpload request is inconsistent with the MD5 calculated by the Object Storage Service (OSS) server.
Causes
The MD5 value specified by the Content-MD5 parameter in the CompleteMultipartUpload request does not match the MD5 value calculated by the OSS server based on the uploaded data.
Examples
For example, you initiate the following request:
POST /multipart.data?uploadId=0004B9B2D2F7815C432C9057C031****&encoding-type=url HTTP/1.1
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Content-Length: 1056
Date: Fri, 24 Feb 2012 10:19:18 GMT
Authorization: OSS qn6q**************:77Dv****************
Content-MD5: 098f6b*****27b4f6
<CompleteMultipartUpload>
<Part>
<PartNumber>1</PartNumber>
<ETag>"3349DC700140D7F86A0784842780****"</ETag>
</Part>
<Part>
<PartNumber>5</PartNumber>
<ETag>"8EFDA8BE206636A695359836FE0A****"</ETag>
</Part>
<Part>
<PartNumber>8</PartNumber>
<ETag>"8C315065167132444177411FDA14****"</ETag>
</Part>
</CompleteMultipartUpload>
The MD5 value of the data that you want to upload is included in the sample request. If the specified MD5 value is inconsistent with the calculated MD5 value of the uploaded data, the error is returned.
Solutions
Make sure that you specify a correct MD5 value and all required part information is included in the XML configuration of the CompleteMultipartUpload request.
References
Is this page helpful?