Caching: CDN
-
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.263 votes -
Access to CDN over SSL / HTTPS
Currently the Azure Storage CDN feature doesn't support SSL, especially SSL using a custom domain. It would be awesome to be able to make use of the CDN feature with an SSL / HTTPS secured website.
203 votesWe support SSL/HTTPS today, with one limitation, which is that we support this only when one uses the CDN domain name (az18283.vo.msecnd.net), we do not support SSL when one uses a CNAME, and although that support is on the list of things to prioritize, it is not in the top half of that list.
-
Automatic HTTP compression on Azure blob CDN (gzip)
We would like to be able to serve static CSS and JavaScript files using the Azure CDN.
To increase performance gzip compression on such files is preferred, or even a must have!
137 votes -
Purge the content of CDN when needed
There have been many cases that I wanted to remove the content of my CDN. For example I make a change to my CSS file, then because this feature is missing I will have to wait a long time for it to be removed automatically. I can not wait that long. I would like a way to remove the CDN content manually or programmatically
68 votes -
http cache (proxy) - CDN-like, geo-aware, highly available
Something like Squid (http://www.squid-cache.org/) or MS ISA server (ISA caching features only), but integrated in Azure, and cached aroud the world, like CDN.
In other words, enable the web-pages to be served via CDN.
(This is not meant to be ASP.NET in-memory cache, not custom cache provider pointing to Azure Storage, and not Squid in the worker role)
20 votes -
Custom origin support to CDN
It would be great if the CDN could be pointed to a custom origin. For example I could run an ASP.NET Web Api at my Azure virtual machine and then point the CDN to that Api.
This is something that the AWS supports.
10 votes -
Allow multiple CNAMES for CDN.
It will make possible more than 6 (typical for modern browsers) simultaneous connections from single client.
8 votes -
HTTP Expires Header or Custom HTTP Headers
Amazon S3 supports adding Custom HTTP Header properties to blob, this gives us more control over how to mange our blobs.
We use simple caching, by default objects are cached for 30 days using Expires headers. And when we want to refresh objects, we pad url with modified version. This gives far better control over any other caching mechanism.
Please add custom headers for blobs.
6 votes
- Don't see your idea?
