Re: [Bug-wget] New wget (1.19.2): Unexpected download behaviour for gzip-compressed tarballs (HTTP-header dependent)

2017-11-01 Thread Daniel Stenberg
On Wed, 1 Nov 2017, Tim Rühsen wrote: Content-Encoding: gzip means that the data has been compressed for transportation purposes only. That's actually not what it means. There's transfer-encoding for that purpose, but that's not generally supported by clients. RFC7231 section 3.1.2.1 [*] sa

Re: [Bug-wget] New wget (1.19.2): Unexpected download behaviour for gzip-compressed tarballs (HTTP-header dependent)

2017-11-01 Thread Jens Schleusener
Hi Tim, On Mittwoch, 1. November 2017 17:27:58 CET Jens Schleusener wrote: Hi, the new "wget" release 1.19.2 has got a new feature: "gzip Content-Encoding decompression" But that feature - at least for my self-conmpiled binary - leads to a problem if one downloads gzip-compressed tarballs

Re: [Bug-wget] New wget (1.19.2): Unexpected download behaviour for gzip-compressed tarballs (HTTP-header dependent)

2017-11-01 Thread Tim Rühsen
Hi Jens, On Mittwoch, 1. November 2017 17:27:58 CET Jens Schleusener wrote: > Hi, > > the new "wget" release 1.19.2 has got a new feature: > > "gzip Content-Encoding decompression" > > But that feature - at least for my self-conmpiled binary - leads to a > problem if one downloads gzip-compre

[Bug-wget] New wget (1.19.2): Unexpected download behaviour for gzip-compressed tarballs (HTTP-header dependent)

2017-11-01 Thread Jens Schleusener
Hi, the new "wget" release 1.19.2 has got a new feature: "gzip Content-Encoding decompression" But that feature - at least for my self-conmpiled binary - leads to a problem if one downloads gzip-compressed tarballs from sites that send for e.g. an HTTP response header containing lines like