[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev lynx 2.8.2 on solaris via proxy - problem
From: |
Klaus Weide |
Subject: |
Re: lynx-dev lynx 2.8.2 on solaris via proxy - problem |
Date: |
Wed, 21 Jul 1999 18:50:49 -0500 (CDT) |
On Wed, 21 Jul 1999, Hodorov, Steven V (Steve), CSCIO wrote:
> Hello,
>
> I'm writing to inform you of a problem I discovered using lynx behind a
> proxy server.
>
> After I defined our proxy in the cfg file and ran lynx, the proxy server
> complained that lynx was using a non-compliant request structure. Instead of
> asking the proxy for HTTP://www.XYZ.com <HTTP://www.XYZ.com> it asks for
> file:/www.XYZ.com.
The "HTTP:" should be "http:" (although normally lynx should canonicalize
that).
When testing, give lynx full "http://..." URLs, don't rely on lynx
guessing or completing the "http:" scheme part.
> we are using the netscape proxy server. But other proxy servers I know off
> all require a valid URL not file:/ ...
You have to specify the contents of http_proxy with a trailing
slash after the host[:port], as shown in lynx.cfg.
If that's not the reason for your problem, you have to give us some
more specific examples. Possibly including -trace output.
> Another (minor) issue: on unix all environment variables are defined
> UPPERCASE (by convention) lynx expects lower case only env vars.
As already noted, it's another convention that lynx inherited.
It only applies for the *_proxy variables.
Klaus