I have been using Spaces in replace of S3 for a while. I am using custom metadata. The retrieval of my custom metadata is fine if I get the objects via either java AWS SDK or AWS CLI. However I cannot get it via javascript running on a domain. I have configured CORS for the bucket and notice that Digital Ocean does not provide a place to enter the ExposeHeaders configuration, which enable S3 CORS to return custom metadata for the objects. I even attempted to set the ExposeHeader myself for my bucket using AWS CLI, something like: aws --endpoint-url https://sgp1.digitaloceanspaces.com s3api put-bucket-cors --bucket mybucket --cors-configuration file://cors.json the cors.json file contains my settings for ExposeHeaders
getting back the CORS from DigitalOcean shows that my settings was saved, with the ExposeHeaders aws --endpoint-url https://sgp1.digitaloceanspaces.com s3api get-bucket-cors --bucket
However, there is still no metadata or any extra headers in my cross domain response . The only headers presented for my objects are: content-type and last-modified.
Is this a missing configuration on DO side? Thanks and regards, Nghia
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
