How can we improve Azure CDN?

Allow different CDN cache and client cache times for Azure CDN Standard

Currently the only option is to set the Max-Age header on the content which sets the TTL on the CDN endpoints AND on the clients.

If we use the Purge API to refresh the CDN content, the clients still have the cached version.

Akamai has a "downstream-ttl" attribute on the Edge-control header that allows for client expiration customization while letting the "max-age" header set the CDN expiration.

This way you can set the downstream-ttl to 0 (client always requests to CDN) while CDN can cache the original content until Purged.

Without this, the Purge command is not entirely useful.

15 votes
Vote
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Matias Quaranta shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
planned  ·  Anton Kucer [MSFT] responded  · 

I’ve updated the title to reflect this is a request for Azure CDN Standard as this is supported via the rules engine in Azure CDN Premium from Verizon. Suppport for this is targeted for availability later this year in CDN Standard from Akamai and Verizon.

1 comment

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base