[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] Unexpected behavior downloading Lynx's binary
From: |
Thorsten Glaser |
Subject: |
Re: [Lynx-dev] Unexpected behavior downloading Lynx's binary |
Date: |
Sun, 1 Jan 2017 02:30:06 +0000 (UTC) |
Thomas Dickey dixit:
>> According to the trace log, the server sent "Content-Encoding: gzip"
>> in the response header in both cases. I think the client should
>> store uncompressed files in these cases.
>
>hmm - just ".tar" ?
>
>(but then the server would not provide bzip2...)
No.
What he means (I think — I occasionally experience a similar problem)
is that content served with a “Content-Encoding: gzip” header should
be decompressed by lynx before being saved by the (D)ownload process
(or passed to a DOWNLOADER utility).
bye,
//mirabilos
--
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.