Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
DOCTL "Access Token is Required" even after initializing Question Question
i can not connect my Database to my webservice Question Question

Question

XAmzContentSHA256Mismatch when trying to upload image via the Spaces API

Posted September 18, 2017 4.9k views
API

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.

Add a comment
qaa0aa9baf4a3d060b76d049e2
By:
qaa0aa9baf4a3d060b76d049e2

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
DOCTL "Access Token is Required" even after initializing Question Question
i can not connect my Database to my webservice Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
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”.

Reply Report
renatoechevarriavidasoft November 28, 2017

Bump

Reply Report
jmbjr March 1, 2018

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

Reply Report
luissndr June 13, 2018

I’m having the same problem

Reply 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.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help