Ability to force the CDN to refresh a specific blob from Azure Blob Storage
A new API to send a request to the CDN so that it invalidates an previously cached blob and forces a refetch from Azure Blob Storage.
This would happen regardless of the original Cache Control header set for the blob.
Frank van Eykelen commented
According to this article from 2011 it's "under development":
"As of 1.4, no purge function is available. This feature is under development."
This feature request needs to be rephrased: Implement an API which permits purging items from the cache.
I bet if the feature name was changed, you'd suddenly get LOTS AND LOTS of votes for this!
Pete @ Philtinium commented
Or just simply a mechanism to invalidate the CDN's for a blob in the Azure portal. Again I can't believe there are not more votes for this as I would have thought this a useful mechanism for anyone changing there static content on a regular basis i.e. developing sprites or JS/CSS. Currenty I have TTL of 1 day but when I launch a new version I don't want to wait a day for the content to catch up with the new release.
guy rafa commented
any reliable CDN offers purge services. in the current settings and upload takes upto 72 hours!
what happens if we upload a a version with bug we will lose revenue for 72 hours till the cash is cleared form all end points ?
Valli Kamakodu commented
Seriously, only 26 votes for this?. We have a file on CDN that's cached for 6 months that needs to be taken down immediately or face serious consequences. There is no way right now to force the CDN to flush out the cache before it expires and hence users will have unintended access to this file for few more months!!!.This is a must feature.
Amazon can do it, why Microsoft can't ...