Actually, yes it does, or it can if compiled to support JavaScript. there
are even links packages for DOS that both support JavaScript and work on
this site.
What personally bugs me about links the chain, at least in stand alone
form, is its inability to support cookies, or speak very well.
Kare
On Fri, 12 Nov 2021, Travis Siegel wrote:
As far as I know, links doesn't support javascript, but it works on their
site. <sahrug>
On 11/12/2021 1:36 PM, Rudy Vener wrote:
Hi Ian,
Okay, so I modified my lynx.cfg to use HTTP_PROTOCOL:1.1 and
to enable its setting in the lynxrc file.
Set my user agent to:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; XH; rv:8.578.498) fr,
Gecko/20121021 Camino/8.723+ (Firefox compatible)
and tried to access http://www.realclearpolitics.com once more.
and get a landing page with this:
Please enable JS and disable any ad blocker
It looks like they just aren't going to allow any browsers that don't
support javascript.
Or am I missing something else?
On Thu, 11 Nov 2021, Ian Collier wrote:
I find it interesting that Lynx cannot verify the certificate of
'realclearpolitics.com' (without the www) because the server is
not returning the certificate chain. But with the www is a completely
different server which does have a valid certificate.
Anyway I have found that links (the chain) will display the web site
correctly by default, but gets denied if I supply any one (or more)
of the following options:
-http-bugs.no-compression 1
-http-bugs.http10 1
-http.fake-user-agent Lynx
So as far as Lynx (the cat) is concerned, what we need to do in order
to visit this site is (a) change the user agent, and (b) enable HTTP
1.1.
Enable HTTP 1.1 can be done either in the Options screen or in
lynx.cfg.
User agent can be done either in Options or on the command line. My
experimentation shows that they want at least your OS in the user
agent,
so "Lynx (Linux 5)" works, while Lynx's default user agent does not
because it doesn't contain the OS name.
imc
--
ent-