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.
We really need this fixed, ideally we would like to plug into some form of Cloudflare API to be able to clear the cache for a specific Image or Asset.
We cant just reduce the max-age down to a couple of minutes as this affects the CWV scores
We cant add versioning behind the URLs as for certain scenarios we are dynamically fetching images based off product code.
Hi Anna,
As mentioned in the ticket primarily it would be for deployment scenarios such as clearing specific non versioned URL from the CDN cache rather than having to clear the entire cache. But clearing both specific URLS and the whole CDN would be good to build in to the deployment pipelines where we need it.
Having the option to force delete a specific URL such as a cache static page, image or asset as part of the CMS would also however be great. Just more control on the caching than the full clear in the PaaS portal to only those users via an API would be good (such as cloudflare has itself).
Hi Anna,
It would be great to have an API that allows us to clear specific URLs from the cache. We have an automated process that updates data every 15 minutes, independent of CMS publishing.
Hey Anna,
I think both of those examples are ideal. Sometimes when we publish some PDFs, the content is cached by Cloudflare and not updated when the new version is updated. We had to work around that by including the published date in links to those documents. Ideally when a content item is published, the link could be sent along to Cloudflare and the cache item for that file could be invalidated.
Additionally, when code is pushed to an environment, it would ideally automatically clear the cloudflare cache.
Cheers
Hello! Could folks please elaborate on where an automatic CDN cache purge would be most beneficial? For example, publishing changes to content in the CMS (and on specific pages) or upon a deployment of the source code in DXP?
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