Enabling HTTP 304 Caching with ETag

We are trying to enable HTTP compression (gzip) and HTTP 304 Caching via ETags on Azure CDN. We already discovered an issue with enabling Azure CDN Compression, but now we can't get compression and ETag caching (304s) working simultaneously. This issue has been posted to Azure forums here.

Here is an example of the compressed, but not HTTP cacheable (304) link:

https://xxxx.vo.msecnd.net/resourceManager.axd?token=HL80vX5hf3lIAAA&group=core.js

Here is an example of the cacheable (304), but not compressible (gzip) link:

https://xxxx.vo.msecnd.net/resourceManager.axd?token=HL80vX5hf3lIAAA&group=core.png

Does anyone know how to get HTTP Caching (304s) and HTTP Compression working together on the Azure CDN?

---

It is important to know if you are specifying If-None-Match or If-Match ? Based on my experience, most users rely on modification date and GET If-Modified-Since .

ETag is stronger if you need to a cache flag for a given entity with multiple encodings, etc.

For your requirement please use Modified/If-Modified-Since and you don't need variable caching based off encodings and this should work.

More info is here: HttpWebResponse LastModified

链接地址: http://www.djcxy.com/p/10754.html

上一篇: 具有多个https站点的HAproxy

下一篇: 使用ETag启用HTTP 304缓存