3 ms·
This website is sending gzip _and_ ignoring the client Accept-Encoding header. Specifiying "identity" has no effect. Ignoring the Accept-Encoding header is co
by 1vuio0pswjnm7 2y ago
This website is sending gzip _and_ ignoring the client Accept-Encoding header. Specifiying "identity" has no effect.
Ignoring the Accept-Encoding header is common but sending gzip compressed response body and _also_ ignoring the header, thereby making it impossible for the client to disable compression using Accept-Encoding: identity, is relatively rare.
Another example that comes to mind is www.amazon.com. However in that case one can disable compression by sending a Viewport-Width header.
- cqqxo4zV46cp 2y agoThere is, in reality, nothing unusual about that.
- 1vuio0pswjnm7 2y agoThey have now fixed it after I submitted this comment. No longer sending gzip by default. Thanks for that. Someone tell Amazon they should do the same.
- 1vuio0pswjnm7 2y agoIn addition to viewport-width www.amazon.com also requires a user-agent header in order to disable compression
- 1vuio0pswjnm7 2y agoSadly another example is now www.sec.gov. They require a value of "deflate, gzip" for Accept-Encoding. Other sec.gov subdomains do not have this restriction. FTC, who also uses Akamai, does not have it. Weird.