lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev Alert: this client does not contain support for HTTPS urls.


From: Doug Kaufman
Subject: Re: lynx-dev Alert: this client does not contain support for HTTPS urls.
Date: Tue, 11 Aug 1998 20:03:23 -0700 (PDT)

On Tue, 11 Aug 1998, Jacob Poon wrote:

> Wait, if you can configure current Lynx code to support https URL (via
> proxy method), shouldn't that be available in the manual?  Anyway, with

The lynx.cfg file has a place to designate the https_proxy. The help
files, in the Supported URL's section, gives a link to Subir's page,
which gives further links to the US and European sites for the files and
information on the proxies.

> - The SSL is obsolete for proxy method.
> - The US export laws cannot possibly bother the unpatched Lynx source
> without banning the Lynx sources altogether. 
> - It is possible to re-code Lynx to use only externals for all https
> support, without fear of US export laws, and make https patch into
> history. However, the availability of https connections will depend on the
> existence of binary that provides https connections, which Lynx currently
> cannot include. 

I am not quite sure that I understand. The EXTERNAL mechanism is still
awkward, with no mechanism to make these the default handling of the
URL. You still need to use "." rather than one of the Right Arrow
equivalents to activate the link. Bobcat has the possibility of
AUTO_EXTERNAL, but this has not been ported by Wayne to the mainstream
lynx. The proxy mechanism works smoothly for using an external program.
Unfortunately, DOS doesn't support daemons (as far as I know) or I just
don't know how to make it work entirely in the DOS OS. For security
reasons, you wouldn't want a https proxy on another machine.
                            Doug
__
Doug Kaufman
Internet: address@hidden (preferred)
          address@hidden

reply via email to

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