2 ms·
"How does this advice stack up against the recent security issues with compressed HTTP traffic?" It doesn't. The recent issues with HTTPS suggest there may be
by jerf 13y ago
"How does this advice stack up against the recent security issues with compressed HTTP traffic?"
It doesn't. The recent issues with HTTPS suggest there may be a fundamental tension there between performance and security. In fact the recent issues don't particularly care "where" in the HTTPS connection the compression occurs, it just has to be inside of it. It won't matter whether you use standard HTTP compression or roll your own (which on the TCP socket won't look all that much different anyhow, you'll just be giving up browser support for automatic decompression).