Thanks everyone. Confirmed this is working now.
Kevin
On Tuesday, February 26, 2019, 5:15:58 AM PST, Willy Tarreau <w...@1wt.eu>
wrote:
Hi all,
On Tue, Feb 26, 2019 at 01:29:54PM +0100, Cyril Bonté wrote:
> > De: "Tim Düsterhus" <t...@bastelstu.be>
> > À: "Cyril Bonté" <cyril.bo...@free.fr>, "Willy Tarreau" <w...@1wt.eu>,
> > "Kevin Mao" <kevin....@yahoo.com>
> > Cc: haproxy@formilux.org
> > Envoyé: Mardi 26 Février 2019 12:12:33
> > Objet: Re: Wrong sha256 checksum for HAProxy 1.8 and 1.9?
> >
> > Willy,
> > Cyril,
> >
> > Am 26.02.19 um 10:52 schrieb Cyril Bonté:
> > > Interesting, in fact the downloaded file is a gzip of the tar.gz
> > > itself.
> > >
> >
> > Yes. This appears to be a misconfiguration in either HAProxy or
> > Apache.
> > Probably Apache, because the `.tar.gz` is delivered with Content-Type
> > application/x-tar which I suspect causes HAProxy to compress it once
> > again:
>
> Well, this is more a browser bug than a misconfiguration. But for now, the
> configuration requires a workaround to not use "Content-Encoding: gzip" for
> gzipped files.
> https://bugzilla.mozilla.org/show_bug.cgi?id=610679
> https://bugzilla.mozilla.org/show_bug.cgi?id=902503
It's indeed a bug in the configuration. Recently I noticed that the
compression ratio went down drastically and thought we had a bug
somewhere in the compression code. I captured a lot of traffic and
figured that it's just caused by a number of bots retrieving many
objects without advertising support for compression, so there was
nothing alarming. But I also found a lot of uncompressed responses
due to the content-type that didn't match. I finally extended it,
but apparently too much since it now supports "application/" to
cover jaavascript, html and whatnot. I just forgot it would also
cover tar.gz etc.
We have limited configuration abilities on the compression, I'd like
to have a set of http-request+http-response disable-compression rules
so that we can decide based on a number of arbitrary criteria. At the
very least we'd need to have the ability to compress except for certain
types, but it would be a waste of time to implement something this
limited now.
I've just restarted haproxy with the modified config, the issue should
be gone now. Otherwise don't hesitate to let me know.
Thanks!
Willy
