Cyril, Am 26.02.19 um 14:10 schrieb Tim Düsterhus: > 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. >> https://bugzilla.mozilla.org/show_bug.cgi?id=610679 >> https://bugzilla.mozilla.org/show_bug.cgi?id=902503 >> > > 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` (https://superuser.com/a/960710/107543) indicates > that this is not a browser bug, but rather actual double compression. >
Scratch that, please. You are correct of course. The web browser should strip one of the gzip layers, because the Content-Encoding is properly set to `gzip`. Thus a .tar.gz (with an incorrect mime type), matching the file on the server, remains. Best regards Tim Düsterhus
