[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] application/x-iso-8859-1 D)ownload, or C)ancel

From: Thomas Dickey
Subject: Re: [Lynx-dev] application/x-iso-8859-1 D)ownload, or C)ancel
Date: Tue, 12 Oct 2004 14:46:37 -0400 (EDT)

On Tue, 12 Oct 2004, [ISO-8859-1] Fr?d?ric L. W. Meunier wrote:

> Anybody know why a search on
> (extracted from
> to remove JavaScript) returns
> the Subject ? Then, if I press 'D', it downloads the search
> results. ELinks works fine with it.

I see the problem.  Here's the header:

Date: Tue, 12 Oct 2004 18:27:14 GMT
Content-Length: 15388
Content-Type: text/html
Cache-Control: no-cache
Server: Resin/2.1.12
Content-Encoding: ISO-8859-1
Via: 1.1 CACHE-03 (NetCache NetApp/5.6.1)

The value for Content-Encoding isn't supposed to be a charset (according
to RFC-2068, section 3.5).  Lynx is looking for things that are not one
of: 8bit, 7bit or binary, and assumes it is compressed if it is not one of
those.  This was old code (I see by the diffs that I made a function out
of it in 2.8.5dev.10 2002/10/12).  I'll change that to correspond to the
values that lynx supports for compression, e.g., gzip, compress, bzip2,

(e)links(2) is said to ignore content-type (I haven't looked recently).

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]