Question
Question
Does DO Spaces support caching signed URLS?
If I generate a signed URL with the CDN endpoint I get a SignatureDoesNotMatch error. If I generate the signed URL with the normal (non-CDN) endpoint and manually replace sfo2.digitaloceanspaces.com with sfo2.cdn.digitaloceanspaces.com, it appears to work, but I believe this is actually caching the entire signed URL, meaning that if I generate a new URL for the same object it won’t come from the CDN because the query parameters are different. Is there support for signed CDN URLs like there is on CloudFront? I’ve found a post on the ideas website, but it hasn’t been updated in a while. Is this currently possible or something coming soon?
I’ve got the same question! The Spaces built-in CDN is not usable for us since we can’t cache signed URLS. Having this would be a killer-feature for us to entirely move from S3 to DO Spaces.