Customer Feedback
We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
I agree. It would be great to have an API to purge CDN cache. It would be even better if there was an API to purge cache of a specific URL. Sometimes clients just want to purge the cache for some pages not all because purging all CDN cache can put a lot of load on the web site afterwards.
Bumping this request to assist with issues occuring with cachbusting not working on js script files
Returning to this request that's been in the roadmap for 4 years as it's been re-raised in a discussion in the MVP slack. Optimizely any update on this as it also would help with issues on the edge image resizing beta
Yes, that's great for new projects. I already have been using versioning as standard for new builds but we have a load of legacy projects passed over from other agencies (as a lot of agencies do) and it's not always easy proposition to rework the way these projects work, especially without time and budget to do so.
Also any statically cached assets such as images or controller level page cache that's a little more tricky. In normal scenarios I might intelligently add some initialization code and use the CDN API but I've requested this before and it's not something Epi will give me
Hi Scott, thanks for this feedback. We have this in the roadmap, meanwhile you're waiting for this we recommend you to look at e.g. versioning etc to avoid the need for CDN purge when doing deployments. Regards, John