Problem description
The x-oss-meta-client-side-encryption-part-size header is missing from the InitiateMultipartUpload or UploadPart request in client-side encryption scenarios.
Causes
In client-encryption, the x-oss-meta-client-side-encryption-part-size header is required for the InitiateMultipartUpload and UploadPart requests.
Examples
For example, you initiate an InitiateMultipartUpload request:
POST /multipart.data?uploads HTTP/1.1
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Date: Wed, 22 Feb 2012 08:32:21 GMT
x-oss-storage-class: Archive
Authorization: OSS qn6q**************:77Dv****************
x-oss-meta-client-side-encryption-key: val0
x-oss-meta-client-side-encryption-start: val1
x-oss-meta-client-side-encryption-cek-alg: val2
x-oss-meta-client-side-encryption-wrap-alg: rsa
x-oss-meta-client-side-encryption-magic-number-hmac: val4
x-oss-meta-client-side-encryption-data-size: val5The error is returned for the request because the x-oss-meta-client-side-encryption-part-size header is missing from the request body.
Solutions
Include the x-oss-meta-client-side-encryption-part-size header in the InitiateMultipartUpload and UploadPart requests in client-side encryption scenarios.