Re: Double compression over HTTPS

On Fri, Oct 5, 2012 at 12:15 PM, Bert Huijben <bert_at_qqmail.nl> wrote:
> +1 on this.
>
>
>
> Can you see if zlib is being used (after negotiation) before requesting
> compression from the Server?
>

It's possible, openssl has functions SSL_get_current_compression and
SSL_get_current_expansion for this purpose.
I'll have to check how they can fit in with the lazy initialization
used by serf though.

> Just checking if the feature is available in openssl doesn’t tell if the
> feature is compiled in at the other side.
>
>
>
>
>
> Using 1m9 (=69 seconds) and 109 seconds in the same table, hides the major
> difference between the numbers.

Indeed. This is the table with all times in seconds:
   | bytes read | bytes written | total time
1: | 17.50MB | 233-284KB | 59s
2: | 18.67MB | 2.13-2.43MB | 69s-78s
3: | 50.35MB | 2.34MB | 103s-108s
4: | 15.27MB | 235-260KB | 50s-56s

>
>
> We should clearly avoid accidentally having no compression at all unless
> requested, as the double compression works much better than that scenario.
>
>
> Bert
>

Lieven
[..]
Received on 2012-10-05 13:19:21 CEST