How can we improve Azure CDN?

CDN should support ETAGS just like they support last modification date

When performing a request with 'If-Modified-Since' header, CDN correctly respond 304 if data is not modified. But they ignore equivalent ETAGS directive: IF-None-Match and always return OK 200. They should consider it. Just as described in RFC 7234.

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

This is a limitation just with Azure CDN from Akamai. With Azure CDN from Verizon ETag support is enabled by default. Supporting ETags is an optional and not a mandatory header per HTTP RFC. We are working long term to mitigate / remove differences in caching behavior between Verizon and Akamai.

1 comment

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...
  • Mark-Anthony Mifsud commented  ·   ·  Flag as inappropriate

    If-Modified-Since works well with second call from 1 user. Can i have cdn verizon add an if-modified-since header when missing as call is coming from a new user browser. In this case the server behind verizon has an if-modified-since filled by cdn with creation date of cache.

Feedback and Knowledge Base