We have implemented signed URLs with spaces and DO CDN. The overall implementation is working well. We are trying to see if different signed URLs to the same asset will use the same CDN cache or will it create a different cache object based on the URL parameters? I am not able to see any access logs to spaces or headers if the file is fetched from the CDN or spaces directly. Does anyone have experience with this?
Ex signed URL from our staging env https://staging-bucket-name.ams3.cdn.digitaloceanspaces.com/ex-file-name?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ABC&X-Amz-Date=20220125T081224Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=ASIG454
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!
Hey @jonaseliasson,
Indeed as you mentioned such a log is not available but it sounds like a great idea, sounds like it’d be super useful!
The best thing to do to get your voice heard regarding this would be to head over to our Product Ideas board and post a new idea, including as much information as possible for what you’d like to see implemented.
What I would personally do is to use curl -IL your_url to check the exact headers that are returned by the specific URL.
Hope that helps!
- Bobby.
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.
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.