I'm using Akamai General Web Delivery. Its seems fine but Purge all and on the images files specific have not able the set Leverage Browser Caching (expire headers). Its maybe easly be on the Azure control panel.2 votes
Both of these capabilities are in our backlog for making available via Azure CDN from Akamai later this year.
Currently we are only serving static content through CDN, it would be nice to serve dynamic content with cookies etc, where CDN kind of acts as a Forward HTTP Proxy instead of CDN. Benefit will be of multiplexing HTTP traffic to single host.1 vote
We need more details on what you are looking for regarding “multiplexing HTTP traffic to a single host” The CDN is built as a reverse proxy and can be used for both static and dynamic content. For dynamic content that you don’t want to be cached by the CDN you can either set the appropriate cache control header (e.g. max-age) or use the bypass cache capability in the rules engine in the Azure CDN Premium to control this for specific content. Long term we are working on enabling this capability also in Azure CDN Standard.
Ability to use WAF with OWASP CRS, and turn on/off specific rules1 vote
Give free a CDN that is ready for use, except for some parameters to be specified and the necessary files to be uploaded. Something like a template.
The videos where experts give lectures are only for other experts to applaud. The majority of your prospective clients are businessmen, educators, etc., who do not want to become experts in IT and do not have the time.1 vote
What specific use case scenarios are you looking for this capability? For a # of end-to-end scenarios in Office 365 (e.g. Office 365 Video) we already enable CDN seamlessly without any user interaction needed or additional cost.
Renewing Assets by hand is very hard if there are many target assets.
Hoping the renewing automatically.1 vote
HTTP/2 is supported as a protocol but is effectively broken and resources are delivered out of order. It takes coordination of the software stack from the edge server through to the networking stack to make sure excessive data isn't buffered (including on the network with bufferbloat).
Proper prioritization is critical for web performance and particularly for HTTP/2 where the server is responsible for honoring it.
There is a GitHub repository with information on how to test for it as well as tracking support across CDN's and hosting providers: https://github.com/andydavies/http2-prioritization-issues1 vote
For Azure CDN add support uploading certificates signed by Let's Encrypt and/or other ACME providers. Currently you can add Let's Encrypt (ACME) signed certificates to Key Vault but when deploying to the CDN it fails (rejected).1 vote
Please establish servers in Pakistan and Dubai as there are no nearby servers for Pakistan. The minimum latency that we get here in Pakistan is around 250ms which is too high for developing projects and playing online games from your servers.1 vote
On Azure Standard Verizon CDN, if we set origin path for the CDN origin when we set the custom caching rules for the CDN endpoint, we must add the origin path to the beginning of the URL path.
However, this is no description about this on the custom caching rule page.
Could you please add the description on the UI so we will be not confused about this in the future?
Thanks a lot.
- Don't see your idea?