2 ms·
It's a disabling of the optional compression at the TLS layer. HTTP content compression is not affected.
by caf 14y ago
It'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.