0005-00000401

Problem description

The x-oss-meta-client-side-encryption-key request header is missing from a PutObject, InitiateMultipartUpload, or UploadPart request in a client-based encryption scenario.

Cause

For client-based encryption, PutObject, InitiateMultipartUpload, and UploadPart requests require the x-oss-meta-client-side-encryption-key request header.

Sample Problem

The following example shows 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-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: val5
x-oss-meta-client-side-encryption-part-size: val6

The request fails because the x-oss-meta-client-side-encryption-key request header is missing.

Solution

For client-based encryption, include the x-oss-meta-client-side-encryption-key request header in PutObject, InitiateMultipartUpload, and UploadPart requests.

References

• Client-based encryption

• PutObject

• InitiateMultipartUpload

• UploadPart