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!
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.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $200 of credit to try our products over 60 days!