🚀 go-pugleaf

[posted and e-mailed]

>I updated the version of Lynx available from my directory via the
>userbin to version 2.8.1dev6 today. Let me know if anyone has any
>problems with it.

Yes, I encountered a SERIOUS problem with it.  I have verified that my
problem is exhibited only by the new version of Lynx.  Old versions
work, as do other browsers.

The problem is that this new Lynx fouls up a query string contained in a
URL for a CGI invocation.  For example, I have the following link in one
of my web pages:

<a href="http://cgi.unicorn.us.com/cgi-bin/unicorn/mgadmin?getpswd=33536&lg=1">Miami (University of)</a>

Here's how the new Lynx interprets the URL above:

http://cgi.unicorn.us.com/cgi-bin/unicorn/mgadmin?getpswd=xc100b~^I6=1

Note how it mangled the query string.  Needless to say, my CGI
goes off and does something it's not supposed to do.  You can
try it yourself, you won't hurt anything.  Any link on the page
http://unicorn.us.com/guide/programs/a_rg4.html will do this -- you're
supposed to get a log-in prompt (and you do with other browsers) but the
new Lynx will send the CGI off into a "change password" function.

Try it with the new Lynx, then try it with an old Lynx.  Version 2.6 is
available at /usr/local/bin/lynx.

This happens only if you have a page displaying that URL and you step on
it with Lynx.  If you invoke Lynx from the commandline with that URL as
the argument for Lynx (in single quotes so the ampersand won't get
intperpreted as a shell background directive), it works fine.  The URL
will get misinterpreted only if it's already displayed on a web page.

I'd say this is a serious problem.  There are a lot of URLs out there
expressed in an explicit CGI GET format.

-Alex