According AWS S3 documentation - in case using SSE-C API function "UploadPart" need to return next headers: "x-amz-server-side-encryption-customer-algorithm" and "x-amz-server-side-encryption-customer-key-MD5". But in reality response does not contain the headers. That affect on at least AWS s3 .net SDK where there existing of headers are checking: aws-sdk-net.

Expected Behavior

UploadPart response contain SSE headers in case encryption is using

Current Behavior

UploadPart response does not contain SSE headers in case encryption is using

Possible Solution

Add to response headers as described Aws S3 Documentation.
As workaround for code based on Aws S3 SDK: for each upload part set UploadPartRequest.DisableMD5Stream = true, which helps avoid checking the hash for each part when response has been received.

Steps to Reproduce (for bugs)

Just use example Uploading an object using multipart upload -> Using the AWS SDKs (low-level-level API) -> for .Net

Context

I am using Minio as a storage server runned as a docker container and a client based on Aws S3 .net Sdk to communicate with the server.

Your Environment

• Version used (minio --version): RELEASE.2021-03-17T02-33-02Z
• Server setup and configuration: docker container with self-signed certificate for SSL supporting
• Operating System and version (uname -a): Linux f6a5602756bf 4.19.121-linuxkit Full restructure in accordance with #1 SMP Thu Jan 21 15:36:34 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux