XAmzContentSHA256Mismatch when trying to upload image via the Spaces API

September 18, 2017 1.9k views
API
qaa0aa9baf4a3d060b76d049e2
By:
qaa0aa9baf4a3d060b76d049e2

Hi,

I am getting XAmzContentSHA256Mismatch when trying to upload an image via the Spaces API.

Uploading a text/plain works fine, but I am really struggling with image/png.

Using postman, and adding the image in the body as form-data.

Sha256 generated with digest.

Sign In to Comment
5 Answers
ianmjones September 6, 2018

I’ve found that DigitalOcean Spaces does not like signed payloads, which is the default when using things like the AWS PHP SDK v3.

So as well as setting “endpoint”, also set “signature_version” to “v4-unsigned-body”.

Report
renatoechevarriavidasoft November 28, 2017

Bump

Report
jmbjr March 1, 2018

Did you ever find out a fix for this, I am having the same problem.

Report
luissndr June 13, 2018

I’m having the same problem

Report
prnjanuario May 23, 2019

I have a similar problem using https://github.com/ctrox/csi-s3, since it states The provided 'x-amz-content-sha256' header does not match what was computed, it seems that the API is not 100% compatible with S3 API.

Report
Have another answer? Share your knowledge.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Related