[Top][All Lists]

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

Re: [Lynx-dev] HTTP1.1/ 204 NoContent Error

From: Karen Lewellen
Subject: Re: [Lynx-dev] HTTP1.1/ 204 NoContent Error
Date: Mon, 26 May 2014 10:04:00 -0400 (EDT)

You are welcome...I think, if the debian list  comment refers to me.
However, I am not using debian either. Instead my access to lynx is via shell services. <spelling> freebds here at shellworld, or the shell provided by my web hosting company who uses <spelling> ubintu now. Is there a present option in Lynx that will simulate the idea you reference here? I respect the wisdom of not permanently using Gordon's solution. There are not many places where I am forbidden, but just enough for it to be something I would rather have a way to prevent.

On Mon, 26 May 2014, Thorsten Glaser wrote:

Karen Lewellen dixit:

then I tried Gordon's suggestion, unchecked the box, and my information

Often adding "MSIE5" to the User-Agent, or prepending
"Mozilla/5.0 (compatible); " to it will also help.

This avoids not sending the Lynx identifier, while
fooling most “evil” webservers (that restrict based
on the User-Agent) into serving one.

Netcologne’s web presence is one of these, too…

Not sending any User-Agent, especially permanently, is not good.
Consider making you a shell alias, like this:

alias lynxmoz="lynx -useragent='Mozilla/5.0 (compatible); Lynx/2.8.8pre.5 
libwww-FM/2.14 SSL-MM/1.4.1 GNUTLS/2.12.23' "

(This value for Lynx in Debian unstable.)

ah, that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian mailing lists │ sole reason I subscribed to
them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
not strike me as a place for good humour, much less German admin-style humour

Lynx-dev mailing list

reply via email to

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