After reading about how gzip compression works it got me thinking. If the Origin and Proxy server (CDN) both support gzip is adding a Vary: Accept-Encoding
header necessary?
相关问题
- iOS (objective-c) compression_decode_buffer() retu
- ruby 1.9 wrong file encoding on windows
- WebElement.getText() function and utf8
- Does specifying the encoding in javac yield the sa
- Can't configure nginx as a proxy for tomcat wi
相关文章
- WebService 启动调试后,能成功调用函数,但断点进不去任何方法
- Angular CLI: Proxy websocket with proxy.conf.json
- OSX proxy issue with homebrew install
- c# saving very large bitmaps as jpegs (or any othe
- What to do with extra HTTP header from proxy?
- Base64 Encoding: Illegal base64 character 3c
- read xml in UTF-8 in scala
- Firebug console error HTTP 407 Proxy Authenticatio
The
Vary: Accept-Encoding
header has more to do with caching than compression. When theVary: Accept-Encoding
header is present, it tells the client that the file can be cached/is the same whether or not the client requests compression.If for some reason the client has an uncompressed version of the file in its cache, it will know not to subsequently request a compressed version of it again and instead to just use the uncompressed file from the cache.
More here: What does vary:accept-encoding mean?