[Top][All Lists]

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

Re: [Lynx-dev] lynx2.8.7pre.4

From: Thomas Dickey
Subject: Re: [Lynx-dev] lynx2.8.7pre.4
Date: Tue, 26 May 2009 13:23:39 -0400 (EDT)

On Tue, 26 May 2009, Thorsten Glaser wrote:

Thomas Dickey dixit:

* add an Options menu checkbox to tell if Lynx should send a user-agent string.
 Unless the useragent restriction is set, the default for this checkbox is
 off, so that Lynx will not send the string.  The corresponding setting,
 send_useragent, may be saved to ~/.lynxrc, but normally is not -TD

If this means what I think it does, I'm strongly against this option's
new default. Lynx should send a user agent by default, for example so
that people see it's actually used or can optimise for it. The ability
to turn it off is good only in corner cases, like pages that misunder-
stand the "optimise" bit above.

Please explain ;)

Well... I reasoned it out like this: providing an option to suppress the
user agent is no good by itself (since you can already clear the string).
What I wanted was a way to change the _user_'s default behavior, and clear
up the problem, while still allowing them to turn on the user agent string.

(If the problem arises, as reported, from a "standard" Apache module, it's not a lot of use to argue with its maintainer).

Thomas E. Dickey

reply via email to

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