3 ms·
Is this a disabling of compression on both ends? No DEFLATE on either requests or responses? Will a site using HTTPS be able to serve compressed assets (like j
by alanh 14y ago
Is this a disabling of compression on both ends? No DEFLATE on either requests or responses?
Will a site using HTTPS be able to serve compressed assets (like javascript & css)?
If not, we’ll urgently need a way for site devs to whitelist precomputed (and thus immune) static assets for compression.
- caf 14y agoIt's a disabling of the optional compression at the TLS layer. HTTP content compression is not affected.
- alanh 14y agoSo what, exactly, is no longer compressed? Merely the headers themselves, and the content is not affected?
- caf 14y agoPretty much, yes. With the proviso that if you didn't have HTTP Content-Type compression for your content before, then it might still have been compressed at the TLS layer, and won't be now.