Related
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
Question
Question
Question
Spaces presigned putObject response does not have access-control-allow-origin header?
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?
Related
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
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.
×
Thought I should add that the OPTIONS request works, and has the access-control-allow-origin header set properly, but the header is missing from the PUT response.
I have the same issue here. Have you solved the issue?
No, I ended up switching back to AWS
Would be great to have an answer to this. None of the solutions in DO’s community or elsewhere solve the CORS issue..