1 result found

1. Automation for purging the CDN cache

   Currently, when content authors choose to upload image or other media files and replace existing media with the same name, the old replaced media lingers in the CDN cache. The CDN cache can be quickly purged through the PaaS portal, but this is a manual step that requires accessing another site outside the CMS itself.

   It would be good if Optimizely could provide an API to purge the CDN cache. This would allow development around purging the CDN cache.

   But ideally, functionality could be built into CMS for this. When replacing an existing media file with the same name, CMS could have the ability to use the Cloudflare API to purge that file from the cache by URL ("Purge Cached Content by URL" in the Cloudflare documentation at https://developers.cloudflare.com/api/resources/cache/methods/purge/. ).

   Currently, when content authors choose to upload image or other media files and replace existing media with the same name, the old replaced media lingers in the CDN cache. The CDN cache can be quickly purged through the PaaS portal, but this is a manual step that requires accessing another site outside the CMS itself.

   It would be good if Optimizely could provide an API to purge the CDN cache. This would allow development around purging the CDN cache.

   But ideally, functionality could be built into CMS for this. When replacing an existing media file with the same name, CMS… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating