Report this

What is the reason for this report?

Spaces presigned putObject response does not have access-control-allow-origin header?

Posted on June 17, 2020

I’m building a client application that uploads directly to spaces with a presigned URL. It gets a presigned putObject URL to upload the file. I can manually send the PUT request from cURL, which succeeds, but in the browser it rejects the PUT response for not having an access-control-allow-origin header set.

My cors configuration is set to AllowedOrigins: * AllowedMethods: GET, PUT AllowedHeaders: *

Is there something I’m missing to have Spaces respond with the access-control-allow-origin header? Or is it not possible?



This textbox defaults to using Markdown to format your answer.

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

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.

This comment has been deleted

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.