Ability to force the CDN to refresh any cached content
A new API to send a request to the CDN so that it invalidates an previously cached item and forces a refetch from the origin - e.g. Azure Storage.
This would happen regardless of the original Cache Control header set for the blob.
Purge is now supported both via the CDN extension in the new Azure Portal (https://portal.azure.com) and via REST API – https://msdn.microsoft.com/en-us/library/mt634451.aspx. This is currently only available for endpoints that are created using the new Azure Portal. Existing endpoints in the previous version of the portal (i.e. https://manage.windowsazure.com) will be migrated to the new Azure Portal in the beginning of 2016 and at that time purge support will also be available for use with them.
Do we have a date on when this crucial feature will be available?
John Mann commented
Just to confirm -
Responded - June 05, 2015 - Availability later this year
So now that we are in the 4th quarter, do we have a more solid delivery date for this?
It was requested over 5 years ago.
Patrick Michalina commented
Is this coming soon?
GIRAUD Alexandre commented
For a customer, we finally decided to not use anymore CDN while this option is not available, we have so many issues. It's time to annouce this feature very quickly
Zac Reid commented
It's September....what sort of end of year are we dealing with here? 12/31/15 @ 11:59:59?
Verizon Edgcast portal has a purge button....how did we lose that when rebranded as Azure? This is making CDN life quite miserable!
With regularity - the HTTPS CDN endpoint is the one that never lets go of cached content. That's the one we use (of course)
This is really causing us problems right now.
Any update??? This feature is crucial!
Any idea when it will be made available? Quite an important feature...
Asif Ashraf commented
I am thinking WHY WHY they missed it at first place
Kris Bloom commented
has this really been planned for 5 years?
Tobias Zimmergren commented
This is a highly requested feature in all of our projects where we utilize our own custom CDN to host files. Unfortunately we can't live with doing hacks to tune it down to x minutes just to force an expiration, and for enterprise-scale solutions that's really not an option anyway.
Just adding an API endpoing, PowerShell cmdlet or even a button in the Azure Portal would be beneficial to just flush the cache.
My guess, by the way, is that the reason Azure hasn't done this is that it seems like they've outsourced virtually the whole of their cache infrastructure to Verizon: so it's likely not just internal resources that need to be mobilized, but external resources as well. Still, it pretty clearly indicates that they don't consider their CDN to be very important.
This really is critical. Right now, we're having to do awful hacks like set cache expiration down to 5 minutes. That's a long ways from optimal - and expensive, too.
I need this feature too !
Jack Lin commented
It's a must, or we'll be forced to choose something else...
Shintaro Abe (dictav) commented
Pedro Sousa commented
This has been marked as "planned" for almost a year.
I do like Azure, but CDN-wise it's incredibly lacking, particularly comparing with its competitors...
What about a status update or at least some sort of feedback?
Mert Degirmenci commented
This is a must have
Rob Donovan commented
Really need this, is there any date for when this is 'planned'?
It seems like a feature that should be there from day 1 :(
This critical piece of infrastructure is useless without a PURGE operation. Please hurry Microsoft!