[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] lynx word bleeding?
From: |
Ian Collier |
Subject: |
Re: [Lynx-dev] lynx word bleeding? |
Date: |
Wed, 2 Feb 2022 10:50:21 +0000 |
Chime Hart writes:
> Hi All: I still use Shellworld, as well as my own Debian setup. Funny
> thing is I visit
> www.radiotapes.com
> On my machine I only see raw html.
As Mouse says, this site isn't sending a Content-Type header. Lynx
actually has an option for this, and so if Lynxes are treating
it differently it probably means the option differs between
environments.
Extract from lynx.cfg:
.h2 PREFERRED_CONTENT_TYPE
# When doing a GET, lynx expects the server to provide a Content-Type, i.e.,
# the MIME name which tells it how to present data. When that is missing
# lynx uses this value.
#PREFERRED_CONTENT_TYPE: text/plain
You can set this within Lynx on the (o)ptions screen, though by default
it's not saved to disk. You want to set it to text/html in order to
properly view the above page.
Note: I believe there shouldn't be a space between the colon and 'text'
in the lynx.cfg setting - at least it didn't work for me with a space
but did work without. This means there is a bug either in the parser
or in the sample lynx.cfg which comes with Lynx.
imc
Re: [Lynx-dev] lynx word bleeding?, Karen Lewellen, 2022/02/01
[Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Luke, Shellworld Support, 2022/02/09