[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev documentation update: more on environment
|
From: |
Leonid Pauzner |
|
Subject: |
lynx-dev documentation update: more on environment |
|
Date: |
Mon, 4 Jan 1999 16:08:30 +0300 (MSK) |
* Minore fix on environment variables section in Lynx Users Guide,
to made it consistent with lynx.cfg. Remove "environment variables" section
from INSTALLATION, change references to Lynx User Guide in all places.
diff -u old/environm.htm ./environm.htm
--- old/environm.htm Sat Jan 2 01:48:08 1999
+++ ./environm.htm Mon Jan 4 14:26:14 1999
@@ -97,12 +97,12 @@
that can act as firewall gateways and
caching servers. They are preferable
to the older gateway servers (see
- WWW_access_GATEWAY, below). Each protocol
- used by Lynx, (http, ftp,
+ WWW_access_GATEWAY, below).
+ Each protocol used by Lynx (http, ftp,
gopher, etc), can be mapped separately
- by setting environment variables of
- the form PROTOCOL_proxy (literally:
- http_proxy, ftp_proxy, gopher_proxy,
+ by setting environment variables of
+ the form PROTOCOL_proxy (literally:
+ http_proxy, ftp_proxy, gopher_proxy,
etc), to "http://some.server.dom:port/";.
See <a href="#proxy">details and examples</a>.
@@ -343,8 +343,11 @@
proxying for all clients on your system.)
If you wish to override the use of a proxy server for specific hosts or
- entire domains you may use the "no_proxy" environment variable. Here is
- an example use of "no_proxy":
+ entire domains you may use the "no_proxy" environment variable.
+ The no_proxy variable can be a comma-separated list of strings defining
+ no-proxy zones in the DNS domain name space. If a tail substring of the
+ domain-path for a host matches one of these strings, transactions with that
+ node will not be proxied. Here is an example use of "no_proxy":
UNIX
setenv no_proxy "host.domain.dom, domain1.dom, domain2"
@@ -360,10 +363,14 @@
and gopher services (if normally proxied) would still be included,
as would any news or wais services on other hosts.
+ Warning: Note that setting 'il' as an entry in this list
+ will block proxying for the .mil domain as well as the .il domain.
+ If the entry is '.il' this will not happen.
+
If you wish to override the use of a proxy server completely (i.e.,
globally override any existing proxy variables), set the value of
- "no_proxy" to "*".
-
+ "no_proxy" to "*". This is the only allowed use of * in no_proxy.
+
Note that Lynx treats file URLs on the local host as requests for
direct access to the file, and does not attempt ftp if that fails.
It treats both ftp URLs and file URLs on remote hosts as ftp URLs,
@@ -374,9 +381,10 @@
Other WWW clients may require that the http server's configuration
file have "Map file:* ftp:*" in it to perform that conversion.
- The proxy and no_proxy variables also can be set at run time via
- lynx.cfg.
-
+ If you have not set NNTPSERVER, proxy or no_proxy environment variables
+ you can set them at run time via the configuration file lynx.cfg
+ (this will not override external settings).
+
<a name="dos"><em>
Win32 (95/NT) and 386 DOS
</em></a>
diff -u old/installa ./installa
--- old/installa Fri Dec 25 13:24:18 1998
+++ ./installa Mon Jan 4 15:45:28 1999
@@ -778,123 +778,16 @@
VII. Setting environment variables before running Lynx (optional)
-1. Unix and VMS
- To set your site's NTTP server as the default host for news reading
- and posting via Lynx, set the environment variable NNTPSERVER so that
- it points to its Internet address. The variable "NNTPSERVER" is used
- to specify the host which will be used as the default for news URLs.
+1. All ports
- UNIX
- setenv NNTPSERVER "news.server.dom"
+ Lynx Users Guide describe a complete set of environment variables
+ used by Lynx. This could be checked later along with reading lynx.cfg
+ after you have installed Lynx.
- VMS
- define/system NNTPSERVER "news.server.dom"
+2. Win32 (95/NT) and 386 DOS
+ These ports cannot start before setting certain environment variables
- The environment variables "ORGANIZATION" or "NEWS_ORGANIZATION", if set,
- will be used for the Organization: header in news postings. (On Unix,
- Lynx also checks for an /etc/organization file.)
-
- The environment variable "LYNX_CFG", if set, will override the default
- location and name of the global configuration file (lynx.cfg) that was
- defined via the constant "LYNX_CFG_FILE" in userdefs.h. See userdefs.h
- for more information.
-
- The environment variable "LYNX_TEMP_SPACE", if set, will override the
- default path prefix for temporary files that was defined via the constant
- "TEMP_SPACE" in userdefs.h. See userdefs.h for more information.
-
- The environment variable "LYNX_SAVE_SPACE", if set, will override the
- default path prefix for files saved to disk that was defined via the
- constant "SAVE_SPACE" in lynx.cfg. See lynx.cfg for more information.
-
- The variable "WWW_HOME", if set, will override the default startup
- URL specified in any of the configuration files.
-
- Lynx still supports use of gateway servers, with the servers specified
- via the variables "WWW_access_GATEWAY", where "access" is lower case
- and can be "http", "ftp", "gopher" or "wais". Most of the gateway
- servers have been discontinued, but "http://www.w3.org:8001"; is
- available for wais searches (note that you do not include a terminal
- '/' for gateways, but do for proxies; see below).
-
- 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 of the form:
-
- UNIX
- setenv http_proxy "http://some.server.dom:port/";
- setenv https_proxy "http://some.server.dom:port/";
- setenv ftp_proxy "http://some.server.dom:port/";
- setenv gopher_proxy "http://some.server.dom:port/";
- setenv news_proxy "http://some.server.dom:port/";
- setenv newspost_proxy "http://some.server.dom:port/";
- setenv newsreply_proxy "http://some.server.dom:port/";
- setenv snews_proxy "http://some.server.dom:port/";
- setenv snewspost_proxy "http://some.server.dom:port/";
- setenv snewsreply_proxy "http://some.server.dom:port/";
- setenv nntp_proxy "http://some.server.dom:port/";
- setenv wais_proxy "http://some.server.dom:port/";
- setenv finger_proxy "http://some.server.dom:port/";
- setenv cso_proxy "http://some.server.dom:port/";
-
- VMS
- define "http_proxy" "http://some.server.dom:port/";
- define "https_proxy" "http://some.server.dom:port/";
- define "ftp_proxy" "http://some.server.dom:port/";
- define "gopher_proxy" "http://some.server.dom:port/";
- define "news_proxy" "http://some.server.dom:port/";
- define "newspost_proxy" "http://some.server.dom:port/";
- define "newsreply_proxy" "http://some.server.dom:port/";
- define "snews_proxy" "http://some.server.dom:port/";
- define "snewspost_proxy" "http://some.server.dom:port/";
- define "snewsreply_proxy" "http://some.server.dom:port/";
- define "nntp_proxy" "http://some.server.dom:port/";
- define "wais_proxy" "http://some.server.dom:port/";
- define "finger_proxy" "http://some.server.dom:port/";
- define "cso_proxy" "http://some.server.dom:port/";
- (Encase *BOTH* strings in double-quotes to maintain
- lower case for the PROTOCOL_proxy variable and for
- the http access type; include /system if you want
- proxying for all clients on your system.)
-
- If you wish to override the use of a proxy server for specific hosts or
- entire domains you may use the "no_proxy" environment variable. Here is
- an example use of "no_proxy":
-
- UNIX
- setenv no_proxy "host.domain.dom, domain1.dom, domain2"
-
- VMS
- define "no_proxy" "host.domain.dom, domain1.dom, domain2"
-
- You can include a port number in the no_proxy list to override use
- of a proxy server for the host accessed via that port, but not via
- other ports. For example, if you use "host.domain.dom:119" and/or
- "host.domain.dom:210", then news (port 119) URLs and/or any wais
- (port 210) searches on that host would be excluded, but http, ftp,
- and gopher services (if normally proxied) would still be included,
- as would any news or wais services on other hosts.
-
- If you wish to override the use of a proxy server completely (i.e.,
- globally override any existing proxy variables), set the value of
- "no_proxy" to "*".
-
- Note that Lynx treats file URLs on the local host as requests for
- direct access to the file, and does not attempt ftp if that fails.
- It treats both ftp URLs and file URLs on remote hosts as ftp URLs,
- and does not attempt direct file access for either. If ftp URLs are
- being proxied, file URLs on a remote host will be converted to ftp
- URLs before submission by Lynx to the proxy server, so no special
- procedure for inducing the proxy server to handle them is required.
- Other WWW clients may require that the http server's configuration
- file have "Map file:* ftp:*" in it to perform that conversion.
-
- The proxy and no_proxy variables also can be set at run time via
- lynx.cfg.
-
-2. Win32 (95/NT) and 386 DOS (adapted from "readme.txt" by Wayne Buttles and
- "readme.dos" by Doug Kaufman)
+ (adapted from "readme.txt" by Wayne Buttles and "readme.dos" by Doug
Kaufman)
Here are some environment variables that should be set, usually in a
batch file that runs the lynx executable. Make sure that you have enough
@@ -906,7 +799,7 @@
HOME Where to keep the bookmark file and personal config files.
TEMP or TMP Bookmarks are kept here with no HOME. Temp files here.
- USER Set to your login name
+ USER Set to your login name (optional)
LYNX_CFG Set to the full path and filename for lynx.cfg
386 version only:
diff -u old/lynx.cfg ./lynx.cfg
--- old/lynx.cfg Sat Jan 2 01:09:06 1999
+++ ./lynx.cfg Mon Jan 4 15:52:26 1999
@@ -730,7 +730,8 @@
#CHECKMAIL:FALSE
# To enable news reading ability via Lynx, the environment variable NNTPSERVER
-# must be set so that it points to your site's NNTP server (see INSTALLATION).
+# must be set so that it points to your site's NNTP server
+# (see Lynx Users Guide on environment variables).
# Lynx respects RFC 1738 (http://www.ics.uci.edu/pub/ietf/uri/rfc1738.txt)
# and does not accept a host field in news URLs (use nntp: instead of news: for
# the scheme if you wish to specify an NNTP host in a URL, as explained in the
@@ -1013,7 +1014,7 @@
# 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 INSTALLATION). If you have not set
+# 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
diff -u old/lynx.hlp ./lynx.hlp
--- old/lynx.hlp Fri Dec 18 14:03:46 1998
+++ ./lynx.hlp Mon Jan 4 15:56:50 1999
@@ -566,10 +566,9 @@
the form PROTOCOL_proxy (literally:
http_proxy, ftp_proxy, gopher_proxy,
etc), to
- "http://some.server.dom:port/";. See
- the INSTALLATION file in the Lynx dis-
- tribution for additional details, and
- examples.
+ "http://some.server.dom:port/";.
+ See Lynx Users Guide for additional
+ details and examples.
WWW_access_GATEWAY Lynx still supports use of gateway
servers, with the servers specified
@@ -581,8 +580,7 @@
include a terminal '/' for gateways,
but do for proxies specified by PROTO-
COL_proxy environment variables. See
- the INSTALLATION file in the Lynx dis-
- tribution for details.
+ Lynx Users Guide for details.
WWW_HOME This variable, if set, will override
the default startup URL specified in
diff -u old/lynx.man ./lynx.man
--- old/lynx.man Fri Dec 18 14:03:46 1998
+++ ./lynx.man Mon Jan 4 15:58:20 1999
@@ -619,8 +619,7 @@
(http, ftp, gopher, etc), can be mapped separately by setting environment
variables of the form PROTOCOL_proxy (literally: http_proxy, ftp_proxy,
gopher_proxy, etc), to "http://some.server.dom:port/";.
-See the \fBINSTALLATION\fR file in the \fILynx\fR distribution for additional
-details, and examples.
+See \fBLynx Users Guide\fR for additional details and examples.
.TP 20
.B WWW_access_GATEWAY
\fILynx\fR still supports use of gateway servers, with the servers specified
@@ -628,7 +627,7 @@
"http", "ftp", "gopher" or "wais"), however most gateway servers have been
discontinued. Note that you do not include a terminal '/' for gateways, but
do for proxies specified by PROTOCOL_proxy environment variables.
-See the \fBINSTALLATION\fR file in the \fILynx\fR distribution for details.
+See \fBLynx Users Guide\fR for details.
.TP 20
.B WWW_HOME
This variable, if set, will override the default startup URL specified
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- lynx-dev documentation update: more on environment,
Leonid Pauzner <=