Am 26.02.19 um 13:29 schrieb Cyril Bonté:
> 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.

The fact that I was able to reproduce it with `curl` when setting
`Accept-Encoding: gzip` and that the .tar.gz-file is delivered as
`application/x-tar` instead of `application/gzip` or
`application/tar+gzip` ( indicates
that this is not a browser bug, but rather actual double compression.

Best regards
Tim Düsterhus

Reply via email to