>>>Hi,
>>>
>>> When I go to a particular site, normally it works very well.
>>>However, once in a while, when I go to the same address, I get the
>>>following prompt instead of my usual rendered html page:
>>>
>>>Read 1023 bytes of data.
>>>HTTP/1.1 200 Document follows
>>>text/html;charset=iso_8859-1
> ^^^^^
>seems lynx doesn't recognize iso_8859* codepages (only iso-8859*)
>Though assume_unrec_charset should be used...
>perhaps he use antique lynx 2.7 or so.
>
>>>D)ownload, or C)ancel
>>>
>>> From reading the Users Guide, it seems that lynx thinks that it
>has
>>>encountered a binary file. I'm wondering whether somebody could
>tell
>>>me why this is happening. Is it a problem with the server, or with
>>>lynx? Can I fix it somehow? By the way, during the same time when
>>>lynx has this problem, I can still use Netscape to access that site.
>>>
>>> Thanks much for any help in advance.
>>>
>>>John Huang
>>>address@hidden
>
I apologize for not providing more details in my original posting.
The site I sometimes have trouble with is
https://www.edreyfus.com/cgi-bin/login. However, the problem is only
occasional. As it occurs randomly, I can't reproduce the problem
reliably.
I'm using Lynx Version 2.8rel.2 on Redhat Linux 6.0. Now I'm pretty
sure that, as Leonid Pauzner points out, the problem lies in that this
version of lynx doesn't recognize iso_8859-1 (with the underscore
instead of the dash), which is sometimes specified by the server, it
seems.
I would have upgraded to a newer version of lynx, except that the last
time I tried, I couldn't get 2.8.3rel.1 lynx to work with
https://www.edreyfus.com/cgi-bin/login. So I decided to stay with
2.8rel.2. If somebody has succeeded in accessing this site using the
latest lynx, do please let me know, and I'll attempt my upgrade again.
In the meantime, if somebody could kindly point out how I could force
2.8rel.2 to recognize and render "iso_8859-1", I'd appreciate that
very much.
Thanks much.
John Huang