|
From: | James Cloos |
Subject: | Re: [Bug-wget] New wget (1.19.2): Unexpected download behaviour for gzip-compressed tarballs (HTTP-header dependent) |
Date: | Fri, 03 Nov 2017 01:37:55 -0400 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/26.0.60 (gnu/linux) |
>>>>> "TR" == Tim Rühsen <address@hidden> writes: TR> I downloaded/tested thousands of web pages and they behave as if 'Content- TR> Encoding: gzip' is a compression for the transport. Uncompressing it 'on-the- TR> fly' and saving that uncompressed data was the correct behavior. Lots of servers have that misconfiguration; it was recommended in the past and apache defaulted to doing that when grabbing things like tar.gz. The gui browsers had to learn to work around that misconfig. wget also has to. In short, do not uncompress if the destination name has a compression suffix. Or, in that case, test whether the uncompressed data starts with gzip magic and complete one decompression if so, non if not so. And the same for the other compression formats. -JimC -- James Cloos <address@hidden> OpenPGP: 0x997A9F17ED7DAEA6
[Prev in Thread] | Current Thread | [Next in Thread] |