Problem description
The x-oss-meta-client-side-encryption-magic-number-hmac request header is missing from a PutObject, InitiateMultipartUpload, or UploadPart request in client-side encryption scenarios.
Causes
In client-side encryption scenarios, the x-oss-meta-client-side-encryption-magic-number-hmac request header is required in PutObject, InitiateMultipartUpload, and UploadPart requests if the x-oss-meta-client-side-encryption-wrap-alg request header is set to "rsa".
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-data-size: val5
x-oss-meta-client-side-encryption-part-size: val6The request fails because the x-oss-meta-client-side-encryption-wrap-alg request header is set to "rsa" and the x-oss-meta-client-side-encryption-magic-number-hmac request header is missing.
Solutions
In client-side encryption scenarios, include the x-oss-meta-client-side-encryption-magic-number-hmac request header in a PutObject, InitiateMultipartUpload, or UploadPart request if the x-oss-meta-client-side-encryption-wrap-alg request header is set to "rsa".