[KLUG Members] Lynx, Proxies, and illiteracy
Richard Zimmerman
members@kalamazoolinux.org
Mon, 24 Jun 2002 08:43:52 -0500
> I've read the lynx man page oh so many times. Set innumerable environment
> variables like PROTOCOLHTTP, PROTOCOL_HTTP_PROXY to things like
> kohocton:3128, http://kohocton:3128/, etc.... And I can't get this
> $&*()_@ 9fu7*&*($ (*&$*()@@ thing to use the proxy server, it just beeps
> and comes back with "connection refused", duh.... And there is nothing in
> the squidy logs to indicate it even tried. I've set
Maybe I've read this wrong. Have you tried the http_proxy in
/etc/lynx.cfg?
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
# Lynx version 2.2 and beyond supports the use of proxy servers that can act
as
# firewall gateways and caching servers. They are preferable to the older
# gateway servers. Each protocol used by Lynx can be mapped separately
using
# PROTOCOL_proxy environment variables (see Lynx Users Guide). If you have
not set
# them externally, you can set them at run time via this configuration file.
# They will not override external settings. The no_proxy variable can be
used
# to inhibit proxying to selected regions of the Web (see below). Note that
on
# VMS these proxy variables are set as process logicals rather than symbols,
to
# preserve lowercasing, and will outlive the Lynx image.
#
.ex 15
http_proxy:http://towaway:3128/
https_proxy:http://towaway:3128/
ftp_proxy:http://towaway:3128/
gopher_proxy:http://towaway:3128/
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Or possibly a dns problem?
Just a guess...
Goose