@pacalj If you look at AWS documentation for PutObject
https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html . Content-MD5
is not a required field. Meaning if it is not set by the client, the server should not error out, as you have already seen with AWS S3. As far as minio-go
sdk is concerned, content-MD5
cannot be set via PutObjectOptions
as explained in https://docs.minio.io/docs/golang-client-api-reference#FPutObject
Minio-go sets X-Amz-Content-Sha256
in the case of http
connection and Content-Md5
in the case of https
connections. Minio-go's FPutObject
and PutObject
api abstracts both multi-part put
and single part put
into these APIs. In the case of multi-part
PUT, each part will set either X-Amz-Content-Sha256
or Content-Md5
depending on the type of connection. Since the call is abstracted, it is not possible for a user to set Content-Md5
.
I believe IBM Cloud Object Storage
has a bug as it should not error out, even if Content-Md5
is not set.