: Can a random compression level applied on same html output replace HTTPS to an extent? HTTPS is supposedly a secure protocol for data exchange. I'm wondering upon a page request, if I outputted

@Sent6035632

Posted in: #Compression #Https

HTTPS is supposedly a secure protocol for data exchange.

I'm wondering upon a page request, if I outputted data to the client at a different gzip compression level (over the HTTP protocol) each time, would that still be as secure as HTTPS since the raw compressed data (which to humans is garbage) actually being fed to the client is different each time, yet the browser will decompress it perfectly.

Here's an example of what I mean in code. Assume this code forms index.php and the client enters in the same URL every time to access index.php. Here's the code:

<?php
$output="<p>This is a test HTML page to be encoded at a different compression level every time</p>";
$compressed=gzencode($output,rand(1,9));
echo $compressed;
?>


I mean If its feasible and won't wreck my time-to-first-byte too much, I'd rather take this method than to force users to install certificates just to run my site over HTTPS.

Vote Up Vote Down

Login to post a comment!