0005-00000406

Problem description

The x-oss-meta-client-side-encryption-data-size request header is missing from an InitiateMultipartUpload or UploadPart request when you use client-based encryption.

Causes

In a client-based encryption scenario, InitiateMultipartUpload and UploadPart requests must include the x-oss-meta-client-side-encryption-data-size request header.

Examples

For example, consider the following 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-part-size: val6

The request failed because the x-oss-meta-client-side-encryption-data-size request header was missing.

Solutions

When using client-based encryption, include the x-oss-meta-client-side-encryption-data-size request header in InitiateMultipartUpload and UploadPart requests.

References

• Client-side encryption

• InitiateMultipartUpload

• UploadPart