|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
<html>
|
|
Packit |
f574b8 |
<head>
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
<title>URL Schemes Supported in Lynx</title>
|
|
Packit |
f574b8 |
<link rev="made" href="mailto:lynx-dev@nongnu.org">
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"text/html; charset=us-ascii">
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
" Enumerate, describe and provide examples of Lynx's URL support on Unix and VMS. Lynx supports both Web standards and extensions.">
|
|
Packit |
f574b8 |
</head>
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
<body>
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
[http, https |
|
|
Packit |
f574b8 |
telnet, tn3270, rlogin |
|
|
Packit |
f574b8 |
gopher |
|
|
Packit |
f574b8 |
"#file_url">file | ftp
|
|
Packit |
f574b8 |
| wais |
|
|
Packit |
f574b8 |
"#news_url">news, nntp, snews |
|
|
Packit |
f574b8 |
"#newspost_url">newspost, newsreply, snewspost, snewsreply
|
|
Packit |
f574b8 |
| mailto |
|
|
Packit |
f574b8 |
"#finger_url">finger | cso
|
|
Packit |
f574b8 |
| bibp |
|
|
Packit |
f574b8 |
"#exec_url">lynxexec, lynxprog |
|
|
Packit |
f574b8 |
"#cgi_url">lynxcgi| NcFTP
|
|
Packit |
f574b8 |
| internal]
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL Schemes Supported in Lynx
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx handles a number of URL types, that are
|
|
Packit |
f574b8 |
enumerated below. For more details about URLs (Uniform Resource
|
|
Packit |
f574b8 |
Locators) see RFC1738:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"http://www.w3.org/Addressing/rfc1738.txt">http://www.w3.org/Addressing/rfc1738.txt
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"ftp://ftp.rfc-editor.org/in-notes/rfc1738.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1738.txt
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx resolves partial or relative URLs in
|
|
Packit |
f574b8 |
documents with respect to the BASE if one was specified,
|
|
Packit |
f574b8 |
otherwise with respect to the document's absolute URL, using the
|
|
Packit |
f574b8 |
rules described in RFC1808:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"http://www.w3.org/Addressing/rfc1808.txt">http://www.w3.org/Addressing/rfc1808.txt
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
and in subsequent drafts of the IETF:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"https://web.archive.org/web/20130116065936/http://ftp.ics.uci.edu/pub/ietf/uri/">
|
|
Packit |
f574b8 |
Uniform Resource Identifiers (URI) Working Group
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
When entering a URL on the command line to be used as the
|
|
Packit |
f574b8 |
startfile, or at the prompt for a
|
|
Packit |
f574b8 |
“g”oto entry, a partial host field can be
|
|
Packit |
f574b8 |
used and the scheme field can be omitted if the scheme and fully
|
|
Packit |
f574b8 |
qualified domain name can be constructed internally by using the
|
|
Packit |
f574b8 |
URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES definitions in the
|
|
Packit |
f574b8 |
Lynx configuration file. See the explanation of
|
|
Packit |
f574b8 |
those definitions and their use in your lynx.cfg.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
For example, wfbr will be treated as
|
|
Packit |
f574b8 |
http://www.wfbr.edu/, and wfbr/dir/lynx will be
|
|
Packit |
f574b8 |
treated as http://www.wfbr.edu/dir/lynx, but
|
|
Packit |
f574b8 |
gopher.wfbr.edu/11/_fileserv/_lynx will be treated as
|
|
Packit |
f574b8 |
gopher://gopher.wfbr.edu/11/_fileserv/_lynx.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
For files or directories on the local host, a tilde
|
|
Packit |
f574b8 |
(~) is expanded to the path of the account's login
|
|
Packit |
f574b8 |
directory, e.g., ~/foo will be expanded to
|
|
Packit |
f574b8 |
file://localhost/your/login/directory/foo. The tilde
|
|
Packit |
f574b8 |
expansion is done homologously on Unix and VMS.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
On VMS, Lynx also will expand any file or
|
|
Packit |
f574b8 |
directory spec recognizable to DCL into a valid URL, e.g.,
|
|
Packit |
f574b8 |
[] will be expanded to
|
|
Packit |
f574b8 |
file://localhost/current/default/directory.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
These expansions are SOLELY for startfile or
|
|
Packit |
f574b8 |
“g”oto entries! Any partial or relative URLs
|
|
Packit |
f574b8 |
within HTML documents are resolved according to the rules
|
|
Packit |
f574b8 |
specified in RFC1808 and subsequent IETF drafts.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
https URLs:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx handles http URLs exactly as specified
|
|
Packit |
f574b8 |
in RFC1738. The format is:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
http://host:port/path?searchpart#fragment
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
where :port is optional and defaults to :80,
|
|
Packit |
f574b8 |
/path if present is a slash-separated series of symbolic
|
|
Packit |
f574b8 |
elements, and ?searchpart if present is the query for an
|
|
Packit |
f574b8 |
ISINDEX search or the content of a FORM with METHOD="GET". The
|
|
Packit |
f574b8 |
#fragment field if present indicates a location in the
|
|
Packit |
f574b8 |
document to seek for display, based on a NAME-ed anchor or an ID
|
|
Packit |
f574b8 |
attribute within the document, and is technically an instruction
|
|
Packit |
f574b8 |
rather than part of the URL. Lynx will treat ID
|
|
Packit |
f574b8 |
attributes as NAME-ed anchors for all tags in the BODY of a
|
|
Packit |
f574b8 |
document which can correspond to positions in the rendering of
|
|
Packit |
f574b8 |
the document.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The https URL has the same format, but the default port is
|
|
Packit |
f574b8 |
:443.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx relies for https support on external
|
|
Packit |
f574b8 |
libraries (OpenSSL or GnuTLS) whose capabilities have evolved
|
|
Packit |
f574b8 |
over time. In turn, those libraries may depend upon external
|
|
Packit |
f574b8 |
resources for verifying SSL certificates. For instance,
|
|
Packit |
f574b8 |
certification revocation may be provided via the Online
|
|
Packit |
f574b8 |
Certificate Status Protocol (OCSP) which is an external service.
|
|
Packit |
f574b8 |
Without this facility, Lynx may not warn about
|
|
Packit |
f574b8 |
websites using revoked SSL certificates.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
tn3270, and rlogin URLs:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
A telnet URL generally results in
|
|
Packit |
f574b8 |
Lynx spawning a telnet session.
|
|
Packit |
f574b8 |
Lynx implements the complete telnet URL scheme,
|
|
Packit |
f574b8 |
i.e.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
telnet://user:password@host:port
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The user and/or :password fields may be
|
|
Packit |
f574b8 |
omitted, and the @ should be omitted if neither is
|
|
Packit |
f574b8 |
present. The port defaults to :23 when omitted in the
|
|
Packit |
f574b8 |
URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
A tn3270 or rlogin URL is specified
|
|
Packit |
f574b8 |
equivalently, and similarly spawns a tn3270 or rlogin session.
|
|
Packit |
f574b8 |
The actual behavior is dependent on the TCP-IP software installed
|
|
Packit |
f574b8 |
on the local and target hosts.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
It is unwise to include the :password field except
|
|
Packit |
f574b8 |
for URLs which point to anonymous or other public access
|
|
Packit |
f574b8 |
accounts, and for most TCP-IP software you will be prompted for a
|
|
Packit |
f574b8 |
password whether or not one was included in the URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The gopher URL takes the form:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
gopher://host:port/gopher-path
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
where :port is optional and defaults to :70,
|
|
Packit |
f574b8 |
and the /gopher-path is opaque (not fully equivalent to
|
|
Packit |
f574b8 |
the slash-separated series of symbolic elements of http paths) as
|
|
Packit |
f574b8 |
explained in RFC1738. Typically, the gopher-path consists of a
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
"keystrokes/gopher_types_help.html">gophertype
|
|
Packit |
f574b8 |
indicating the file or service type (e.g., 0 or
|
|
Packit |
f574b8 |
I for plain text or an image, respectively, 7
|
|
Packit |
f574b8 |
for a search, or 1 for a directory), followed by a
|
|
Packit |
f574b8 |
platform-specific selector. Any reserved characters in
|
|
Packit |
f574b8 |
the selector should be hex escaped (%hh), including
|
|
Packit |
f574b8 |
slashes, although hex escaping of slashes is not required by
|
|
Packit |
f574b8 |
Lynx in gopher URLs.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx does not overtly support the gopher+
|
|
Packit |
f574b8 |
protocol, and does not represent itself as gopher+ capable when
|
|
Packit |
f574b8 |
communicating with gopher servers. Lynx might
|
|
Packit |
f574b8 |
transmit any (hex-escaped-tab-separated) extended gopher+ fields
|
|
Packit |
f574b8 |
in a URL if an author included them in a document, but is likely
|
|
Packit |
f574b8 |
to mishandle what the gopher server returns in such cases, and
|
|
Packit |
f574b8 |
would not generate and transmit them itself. For pre-formed URLs
|
|
Packit |
f574b8 |
to submit gopher searches, it may be better to use a ?
|
|
Packit |
f574b8 |
rather than hex-escaped tab (%09) as the separator for
|
|
Packit |
f574b8 |
the searchpart in the selector, e.g.:
|
|
Packit |
f574b8 |
gopher://gopher.wfbr.edu/77/_shell/search.shell%20/_shell/walker?lynx*
|
|
Packit |
f574b8 |
Lynx will handle the %09 if you use
|
|
Packit |
f574b8 |
that instead of ?, but other WWW clients may mishandle
|
|
Packit |
f574b8 |
it.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
For the gophertype which signifies HTML (h),
|
|
Packit |
f574b8 |
if the selector begins with GET%20/
|
|
Packit |
f574b8 |
Lynx will convert the gopher URL to an http URL,
|
|
Packit |
f574b8 |
e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
gopher://www.wfbr.edu:80/hGET%20/
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
will become:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
http://www.wfbr.edu/
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The port field will be retained if it is not :80, and
|
|
Packit |
f574b8 |
will default to :70 if it was defaulted originally.
|
|
Packit |
f574b8 |
These conventions were adopted during development of the
|
|
Packit |
f574b8 |
University of Minnesota gopher software to facilitate the
|
|
Packit |
f574b8 |
offering of links to MIME-capable http servers in the listings
|
|
Packit |
f574b8 |
returned by gopher servers, but should be considered Lynxisms and
|
|
Packit |
f574b8 |
UMN Gopherisms.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The file URL is used to retrieve files or generate a directory
|
|
Packit |
f574b8 |
listing on the local host. The host field can be
|
|
Packit |
f574b8 |
localhost or a domain name for the local host:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
file://localhost/path
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If you do not use localhost or a domain name for the
|
|
Packit |
f574b8 |
local host, Lynx will substitute ftp://
|
|
Packit |
f574b8 |
for file:// and treat it as an ftp URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The /path is treated as originating at the root,
|
|
Packit |
f574b8 |
unless you include a tilde (~), e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
file://localhost/~/foo will be converted to:
|
|
Packit |
f574b8 |
file://localhost/your/login/directory/foo
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The latter feature is a Lynxism, is done homologously on Unix
|
|
Packit |
f574b8 |
and VMS, and should be used ONLY in local documents intended for
|
|
Packit |
f574b8 |
Lynx.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
On VMS, the first element of the path, if not a tilde, is
|
|
Packit |
f574b8 |
assumed to be a device, e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
file://localhost/www_root/directory/filename.suffix
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
should be used for:
|
|
Packit |
f574b8 |
www_root:[directory]filename.suffix
|
|
Packit |
f574b8 |
If you are unsure how to specify a file URL in local documents on
|
|
Packit |
f574b8 |
VMS, invoke Lynx with the desired file or
|
|
Packit |
f574b8 |
directory as the startfile using any spec acceptable to
|
|
Packit |
f574b8 |
DCL, and then use the showinfo command (=) to
|
|
Packit |
f574b8 |
see the file URL which Lynx created for it.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The ftp URL has the general format:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ftp://host:port/path;type=[D,I, or A]
|
|
Packit |
f574b8 |
ftp://username@host:port/path;type=[D,I, or A]
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The default port is :21 and the default
|
|
Packit |
f574b8 |
username is anonymous. If username is
|
|
Packit |
f574b8 |
included, Lynx will prompt you for the password.
|
|
Packit |
f574b8 |
For anonymous ftp, Lynx uses your
|
|
Packit |
f574b8 |
personal_mail_address (user@host) as the
|
|
Packit |
f574b8 |
password if it has been defined via the
|
|
Packit |
f574b8 |
“o”ptions menu. Otherwise,
|
|
Packit |
f574b8 |
Lynx uses the dummy password WWWUser.
|
|
Packit |
f574b8 |
(A password can also be embedded in the URL, by replacing
|
|
Packit |
f574b8 |
username with username:password. This is
|
|
Packit |
f574b8 |
strongly discouraged for “real” passwords that must
|
|
Packit |
f574b8 |
be kept secret, since URLs with the completely unencrypted
|
|
Packit |
f574b8 |
password may show up on the screen, in HISTORY and LIST
|
|
Packit |
f574b8 |
pages etc., and may even become visible to remote sites for
|
|
Packit |
f574b8 |
example through Referer headers.) Do not include the @
|
|
Packit |
f574b8 |
if neither username nor :password is
|
|
Packit |
f574b8 |
included.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The ;type= parameter can be used with value
|
|
Packit |
f574b8 |
D, I, or A to force handling of the
|
|
Packit |
f574b8 |
URL as, respectively, a directory listing, binary file, or ASCII
|
|
Packit |
f574b8 |
file. The Lynx ftp gateway normally determines
|
|
Packit |
f574b8 |
this itself, but the parameter can be used if the internal
|
|
Packit |
f574b8 |
procedure draws an incorrect inference about the nature of the
|
|
Packit |
f574b8 |
ftp URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The /path is treated according to RFC1738 for VMS and
|
|
Packit |
f574b8 |
VM/CMS ftp servers. The lead slash (/) is treated purely
|
|
Packit |
f574b8 |
as a separator, not as a designator for the root, and the
|
|
Packit |
f574b8 |
path string if present is treated as in or under the
|
|
Packit |
f574b8 |
login directory. For VMS ftp servers, if you wish to have the
|
|
Packit |
f574b8 |
first element treated as a device rather than file or
|
|
Packit |
f574b8 |
subdirectory name, begin it with a hex-escaped slash
|
|
Packit |
f574b8 |
(%2f), e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ftp://user@myhost/%2fsys$common/syshlp
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
can be used for a listing of sys$common:[syshlp]
|
|
Packit |
f574b8 |
Also, on VM/CMS ftp servers, if the path string begins
|
|
Packit |
f574b8 |
with vmsysu%3a it receives special handling as an SFS
|
|
Packit |
f574b8 |
path, e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
For Unix and Unix-emulation ftp servers, RFC1738 is not
|
|
Packit |
f574b8 |
respected and the lead slash is treated as the root, i.e., the
|
|
Packit |
f574b8 |
/path is handled equivalently to that in file URLs. The
|
|
Packit |
f574b8 |
distinction is irrelevant for anonymous ftp, but matters when
|
|
Packit |
f574b8 |
using ftp for non-anonymous accounts. If you are using ftp with a
|
|
Packit |
f574b8 |
Unix server and do wish to get a listing of the login directory
|
|
Packit |
f574b8 |
or have the path string treated as a file or path under
|
|
Packit |
f574b8 |
the login directory, include a tilde (~) as for
|
|
Packit |
f574b8 |
"#file_url">file URLs, e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ftp://user@myhost/~
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The wais URL is used to retrieve resources using the Wide Area
|
|
Packit |
f574b8 |
Information System protocol. The format is:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
wais://host:port/database
|
|
Packit |
f574b8 |
wais://host:port/database?wais_query
|
|
Packit |
f574b8 |
wais://host:port/database/wais_type/wais_path
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
where :port defaults to :210
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Direct wais support is built into Lynx for
|
|
Packit |
f574b8 |
VMS, and can be compiled into Lynx on Unix.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If only a database is indicated in the URL,
|
|
Packit |
f574b8 |
Lynx returns an ISINDEX cover page for searching
|
|
Packit |
f574b8 |
that database, and will submit your search with the
|
|
Packit |
f574b8 |
wais_query appended. Lynx will convert
|
|
Packit |
f574b8 |
the server's reply into a hit list with URLs that include the
|
|
Packit |
f574b8 |
wais_type and wais_path for retrieving items
|
|
Packit |
f574b8 |
from the hit list.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
nntp, and snews URLs:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The news and nntp URLs are handled by Lynx as
|
|
Packit |
f574b8 |
specified in RFC1738, but for compatibility with other clients,
|
|
Packit |
f574b8 |
Lynx allows inclusion of host and port fields in
|
|
Packit |
f574b8 |
news URLs, which properly should be used only in nntp
|
|
Packit |
f574b8 |
and snews URLs. If not included in news URLs,
|
|
Packit |
f574b8 |
Lynx will use the nntp server pointed to by the
|
|
Packit |
f574b8 |
NNTPSERVER environment variable or configuration symbol (see
|
|
Packit |
f574b8 |
lynx.cfg), with default port :119. A host field must be
|
|
Packit |
f574b8 |
included in nntp URLs, and the port field is optional with the
|
|
Packit |
f574b8 |
same default.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If the URL requires authentication, Lynx will
|
|
Packit |
f574b8 |
prompt you for the username and password. These are cached during
|
|
Packit |
f574b8 |
a session, for reuse on the same host. If $HOME/.newsauth exists,
|
|
Packit |
f574b8 |
Lynx initializes its cache from this file. The
|
|
Packit |
f574b8 |
.newsauth file contents are one line per entry: hostname,
|
|
Packit |
f574b8 |
password and username (in that order) separated by a space.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The formats are:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
news:newsgroup (retrieves list of messages in newsgroup)
|
|
Packit |
f574b8 |
news:messageID (retrieves the message)
|
|
Packit |
f574b8 |
news:* (retrieves list of all available newsgroups)
|
|
Packit |
f574b8 |
nntp://host:port/newsgroup
|
|
Packit |
f574b8 |
nntp://host:port/messageID
|
|
Packit |
f574b8 |
nntp://host:port/*
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
(snews same as nntp, but the default port is
|
|
Packit |
f574b8 |
:563)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The messageID is the message's unique identifier,
|
|
Packit |
f574b8 |
consisting of an identification string and the host of origin for
|
|
Packit |
f574b8 |
the message (ident_string@origin_host).
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx also supports wildcarding via an
|
|
Packit |
f574b8 |
asterisk for listings of news hierarchies or sub-hierarchies,
|
|
Packit |
f574b8 |
e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
news:comp.infosystems.*
|
|
Packit |
f574b8 |
nntp://host:port/comp.infosystems.*
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
(snews same as nntp, but the default port is
|
|
Packit |
f574b8 |
:563)
|
|
Packit |
f574b8 |
This is not in RFC1738 and may not be supported by all other
|
|
Packit |
f574b8 |
clients.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx allows you both to reply to the
|
|
Packit |
f574b8 |
author of a news message via email, and, if news posting has been
|
|
Packit |
f574b8 |
enabled, to send a followup message to the newsgroup
|
|
Packit |
f574b8 |
(see newspost, newsreply, snewspost,
|
|
Packit |
f574b8 |
snewsreply).
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx converts any strings in news messages
|
|
Packit |
f574b8 |
which appear to be a URL with a supported scheme into a link for
|
|
Packit |
f574b8 |
accessing that URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx also supports the newsgroup and message
|
|
Packit |
f574b8 |
number URL scheme:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
news:newsgroup/startNo-endNo (lists message range in newsgroup)
|
|
Packit |
f574b8 |
news:newsgroup/messageNo (retrieves the message by number)
|
|
Packit |
f574b8 |
nntp://host:port/newsgroup/startNo-endNo
|
|
Packit |
f574b8 |
nntp://host:port/newsgroup/messageNo
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
(snews same as nntp, but the default port is
|
|
Packit |
f574b8 |
:563)
|
|
Packit |
f574b8 |
Use of this scheme is not recommended, because the message
|
|
Packit |
f574b8 |
numbers are specific to each nntp server, unlike the unique
|
|
Packit |
f574b8 |
identifiers for news messages.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
newspost, newsreply, snewspost, and
|
|
Packit |
f574b8 |
snewsreply URLs:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
When Lynx receives group listings or articles
|
|
Packit |
f574b8 |
via news, nntp or snews URLs, it also
|
|
Packit |
f574b8 |
checks whether the nntp server supports posting from the
|
|
Packit |
f574b8 |
Lynx user's site, and if so, includes links for
|
|
Packit |
f574b8 |
posting new messages to that server, or for posting followups
|
|
Packit |
f574b8 |
(replies) to previously posted messages. RFC1738, and IETF URL
|
|
Packit |
f574b8 |
drafts through this release of Lynx, do not
|
|
Packit |
f574b8 |
include any schemes for posting to news groups.
|
|
Packit |
f574b8 |
Lynx has long supported newspost and newreply
|
|
Packit |
f574b8 |
URL schemes for posting new messages or sending followups,
|
|
Packit |
f574b8 |
respectively, to standard nntp servers, with default port
|
|
Packit |
f574b8 |
:119. Lynx now also supports homologous
|
|
Packit |
f574b8 |
snewspost and snewsreply URLs for use with SSL capable nntp
|
|
Packit |
f574b8 |
servers.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The formats are:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
newspost://host:port/newsgroup(s) (post a new message)
|
|
Packit |
f574b8 |
newsreply://host:port/newsgroup(s) (post a followup message)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
(snewspost and snewsreply have the same formats, but the
|
|
Packit |
f574b8 |
default port is :563)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If the host field is omitted, it defaults to that pointed to
|
|
Packit |
f574b8 |
by the NNTPSERVER configuration or environmental variable.
|
|
Packit |
f574b8 |
Inclusion of at least one newsgroup in the URL is required, and
|
|
Packit |
f574b8 |
additional groups can be specified as a comma-separated list.
|
|
Packit |
f574b8 |
Wildcarding of newsgroup names is not supported for these URLs.
|
|
Packit |
f574b8 |
For newsreply and snewsreply URLs, if an external editor has been
|
|
Packit |
f574b8 |
defined via the Options Menu, the user is offered an
|
|
Packit |
f574b8 |
option to include the currently displayed document, which
|
|
Packit |
f574b8 |
presumably is a news article with a followup link that
|
|
Packit |
f574b8 |
was activated, and if confirmed, each line of that document is
|
|
Packit |
f574b8 |
prefixed with a right-angle-bracket. The user is expected to edit
|
|
Packit |
f574b8 |
such an inclusion so that only the passages relevant to the
|
|
Packit |
f574b8 |
followup message are retained.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
These URLs can be used as command line startfiles (in which
|
|
Packit |
f574b8 |
case, Lynx will exit after posting the message,
|
|
Packit |
f574b8 |
and the newreply or snewsreply URLs degrade to newspost or
|
|
Packit |
f574b8 |
snewpost URLs, respectively). They also can be used as HREF
|
|
Packit |
f574b8 |
attribute values in any HTML document homologously to
|
|
Packit |
f574b8 |
"#mailto_url">mailto URLs, with the qualification that they
|
|
Packit |
f574b8 |
presently are supported only by Lynx.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The mailto URL is used to provide links that when activated
|
|
Packit |
f574b8 |
can be used to send a comment or the content of a FORM to an
|
|
Packit |
f574b8 |
Internet email address (user@host). The format is:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
mailto:user@host
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The description of the mailto URL in RFC1738 has been
|
|
Packit |
f574b8 |
interpreted by some as allowing only a single recipient, but
|
|
Packit |
f574b8 |
Lynx invented the mailto URL, has always
|
|
Packit |
f574b8 |
supported a series of user@host addresses as a comma-separated
|
|
Packit |
f574b8 |
list, and still does. For compatibility with Explorer,
|
|
Packit |
f574b8 |
Lynx also accepts a semi-colon-separated
|
|
Packit |
f574b8 |
list.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
For compatibility with Netscape, Lynx parses
|
|
Packit |
f574b8 |
any ?subject=The%20Subject appended to the URL, trims
|
|
Packit |
f574b8 |
the URL at the ?, and uses the value as the default
|
|
Packit |
f574b8 |
Subject: for the message or FORM content mailing. This is not
|
|
Packit |
f574b8 |
recommended practice. The preferred way to indicate the default
|
|
Packit |
f574b8 |
Subject: for a LINK or Anchor with a mailto HREF, or a FORM with
|
|
Packit |
f574b8 |
a mailto ACTION, is via a TITLE attribute with the subject string
|
|
Packit |
f574b8 |
as its value, e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
<LINK REV="made"
|
|
Packit |
f574b8 |
HREF="mailto:me@myhost,her@herhost" TITLE="The Subject">
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
<A HREF="mailto:user@host" TITLE="The Subject">...</A>
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
<FORM METHOD="post" ENCTYPE="text/plain"
|
|
Packit |
f574b8 |
ACTION="mailto:WebMaster@host" TITLE="The Subject">
|
|
Packit |
f574b8 |
...
|
|
Packit |
f574b8 |
</FORM>
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Note that a TITLE attribute for FORM is now included in the
|
|
Packit |
f574b8 |
HTML specifications. Some clients use a SUBJECT attribute for
|
|
Packit |
f574b8 |
this purpose in FORM tags, and Lynx recognizes
|
|
Packit |
f574b8 |
that as a synonym for TITLE.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx also will process any
|
|
Packit |
f574b8 |
to=address(es), cc=address(es),
|
|
Packit |
f574b8 |
keywords=word_list and/or body=message fields
|
|
Packit |
f574b8 |
in ?searchpart tack-ons to mailto URLs. The to
|
|
Packit |
f574b8 |
and/or cc values can be single addresses, or comma- or
|
|
Packit |
f574b8 |
semi-colon-separated lists of addresses. All addresses, and any
|
|
Packit |
f574b8 |
body values, will be offered for approval by the user
|
|
Packit |
f574b8 |
before proceeding with a mailing. Any other name=value pairs in
|
|
Packit |
f574b8 |
the ?searchpart will be ignored. Also, if the mailto URL
|
|
Packit |
f574b8 |
is the ACTION for a FORM, any body in a
|
|
Packit |
f574b8 |
?searchpart tack-on will be ignored, because the body of
|
|
Packit |
f574b8 |
the mailing must be constructed solely from the the FORM's
|
|
Packit |
f574b8 |
content. Lynx expects multiple name=value pairs
|
|
Packit |
f574b8 |
in a ?searchpart tack-on to be separated by ampersands,
|
|
Packit |
f574b8 |
as in the original Netscape implementation, and in an equally
|
|
Packit |
f574b8 |
ill-advised IETF draft of that implementation (
|
|
Packit |
f574b8 |
"ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-03.txt">draft-hoffman-mailto-url-03.txt).
|
|
Packit |
f574b8 |
These should be represented as entities (&) in
|
|
Packit |
f574b8 |
the HTML markup. This functionality is generally desired, but the
|
|
Packit |
f574b8 |
IETF backward compatibility principal normally would lead to a
|
|
Packit |
f574b8 |
new scheme being used (e.g., mail:, or smtp:),
|
|
Packit |
f574b8 |
rather than breaking mailto: implementations.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If ENCTYPE="text/plain" is specified for a FORM with
|
|
Packit |
f574b8 |
a mailto ACTION, Lynx will not hex escape the
|
|
Packit |
f574b8 |
name=value pairs of the FORM's content, and will use physical
|
|
Packit |
f574b8 |
newlines instead of “&” or
|
|
Packit |
f574b8 |
“;” to separate the pairs, so that the
|
|
Packit |
f574b8 |
content will be readable directly. Otherwise,
|
|
Packit |
f574b8 |
Lynx will mail the content with the default:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ENCTYPE="application/x-www-form-urlencoded" (“&” separates pairs)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
or:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ENCTYPE="application/sgml-form-urlencoded" (“;” separates pairs)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
if the latter was indicated.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Note that when mailing FORM content Lynx
|
|
Packit |
f574b8 |
wraps any lines longer than 78 characters, to avoid buffer
|
|
Packit |
f574b8 |
overflows in mail software and to ensure reliable transmission
|
|
Packit |
f574b8 |
across gateways. If the ENCTYPE was not text/plain, any
|
|
Packit |
f574b8 |
script which decodes the mailed content should ignore the
|
|
Packit |
f574b8 |
physical newlines and recognize only hex escaped newline
|
|
Packit |
f574b8 |
characters as intended to be present in the decoded content.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If the mailto URL is not the ACTION for a FORM, and if an
|
|
Packit |
f574b8 |
external editor has been defined via the Options Menu,
|
|
Packit |
f574b8 |
the user is offered an option to include the currently displayed
|
|
Packit |
f574b8 |
document. If this option is accepted, each line of that document
|
|
Packit |
f574b8 |
is prefixed with a right-angle-bracket, and the prefixed
|
|
Packit |
f574b8 |
inclusion should be trimmed by the user to just those passages
|
|
Packit |
f574b8 |
relevant to the message which will be sent.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx has full support for the finger
|
|
Packit |
f574b8 |
protocol, but a format for finger URLs has not yet been adopted
|
|
Packit |
f574b8 |
by the IETF. The formats supported by Lynx
|
|
Packit |
f574b8 |
therefore include every possibility not inconsistent with
|
|
Packit |
f574b8 |
RFC1738, including:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
finger://host finger://@host
|
|
Packit |
f574b8 |
finger://host/ finger://@host/
|
|
Packit |
f574b8 |
finger://host/%2fw finger://@host/w
|
|
Packit |
f574b8 |
finger://host/w finger://host/w/
|
|
Packit |
f574b8 |
finger://host/username[@host] finger://username@host
|
|
Packit |
f574b8 |
finger://host/username[@host]/ finger://username@host/
|
|
Packit |
f574b8 |
finger://host/w/username[@host] finger://username@host/w
|
|
Packit |
f574b8 |
finger://host/%2fw%20username[@host] finger://host/username[@host]/w
|
|
Packit |
f574b8 |
finger://host/w/username
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Activating a finger URL will send a request to the finger
|
|
Packit |
f574b8 |
server via port 79 on the host specified. You can include
|
|
Packit |
f574b8 |
:79 in the URL, but no other value is allowed. The
|
|
Packit |
f574b8 |
/w or /%2fw is used to request a full report
|
|
Packit |
f574b8 |
for finger servers which support it, and is not case sensitive
|
|
Packit |
f574b8 |
(i.e., can be /W or /%2fW). Any strings in the
|
|
Packit |
f574b8 |
report which appear to be a URL with a supported scheme will be
|
|
Packit |
f574b8 |
converted into a link for accessing that URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
An alternative way to access finger servers is via gopher URLs
|
|
Packit |
f574b8 |
with port 79 and the plain text (0) gophertype
|
|
Packit |
f574b8 |
specified:
|
|
Packit |
f574b8 |
gopher://host:79/0
|
|
Packit |
f574b8 |
Lynx will handle such URLs equivalently to overt
|
|
Packit |
f574b8 |
finger URLs, including creation of links for any strings which
|
|
Packit |
f574b8 |
appear to be supported URLs.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The cso URL is intended to provide a gateway to CSO/PH (QI)
|
|
Packit |
f574b8 |
servers. The requests are made on port 105 by default
|
|
Packit |
f574b8 |
(:105), with the following overt cso URL format:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
cso://host
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
You also can use a gopher URL format with port 105 and the CSO
|
|
Packit |
f574b8 |
(2) gophertype specified:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
gopher://host:105/2
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx will parse the stream returned by the
|
|
Packit |
f574b8 |
server for the above URLs and create a FORM for submitting
|
|
Packit |
f574b8 |
additional requests (searches) to the server. Any strings in the
|
|
Packit |
f574b8 |
reports returned for these requests (searches) which appear to be
|
|
Packit |
f574b8 |
a URL with a supported scheme will be converted into a link for
|
|
Packit |
f574b8 |
accessing that URL.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx provides built-in support for
|
|
Packit |
f574b8 |
bibliographic protocol (BibP). BibP links are links to published
|
|
Packit |
f574b8 |
works such as books or journal articles, without a predefined
|
|
Packit |
f574b8 |
server. BibP links are intended for resolution by a local bibhost
|
|
Packit |
f574b8 |
server (http://bibhost/) if it exists. Otherwise, resolution is
|
|
Packit |
f574b8 |
performed by a document-specified server or a known global
|
|
Packit |
f574b8 |
server.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
lynxprog URLs:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If execution of spawned commands has been enabled in your
|
|
Packit |
f574b8 |
Lynx image, the lynxexec and lynxprog URLs can
|
|
Packit |
f574b8 |
be used to execute arbitrary system commands or invoke system
|
|
Packit |
f574b8 |
utilities. Any system command and associated switches or
|
|
Packit |
f574b8 |
qualifiers can be used, with the syntax appropriate for a shell
|
|
Packit |
f574b8 |
running Lynx on Unix, or for DCL on VMS,
|
|
Packit |
f574b8 |
e.g.:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
lynxexec:dir/date/size foo:[blah] (VMS)
|
|
Packit |
f574b8 |
lynxexec:ls -l /foo/blah (Unix)
|
|
Packit |
f574b8 |
lynxprog:news
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
(Note, however, that restrictions on acceptable commands or
|
|
Packit |
f574b8 |
utilities may be imposed by the system administrator.)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
You optionally can include //localhost/ in the URL,
|
|
Packit |
f574b8 |
between the scheme field and the command, but that is always
|
|
Packit |
f574b8 |
implied. The lynxexec and lynxprog URLs differ only in that with
|
|
Packit |
f574b8 |
lynxexec you are prompted to enter RETURN before
|
|
Packit |
f574b8 |
Lynx clears the screen and restores the
|
|
Packit |
f574b8 |
previously displayed document, so that you can read any screen
|
|
Packit |
f574b8 |
output generated by the spawned command, whereas no such pause is
|
|
Packit |
f574b8 |
imposed upon exit from the utility invoked via lynxprog.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
These are Lynxisms and should be used only in local documents
|
|
Packit |
f574b8 |
intended solely for Lynx.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The lynxcgi URL is implemented only on Unix, can be used as
|
|
Packit |
f574b8 |
the ACTION for a FORM, and if enabled in your
|
|
Packit |
f574b8 |
Lynx image has the format:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
lynxcgi://localhost/path_to_CGI_script
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
where //localhost is optional and always implied; the
|
|
Packit |
f574b8 |
full path should be specified, as “~” is not
|
|
Packit |
f574b8 |
recognized; if the script is in the directory
|
|
Packit |
f574b8 |
Lynx was started from, the simple file name is
|
|
Packit |
f574b8 |
adequate. The output of the script should be text/html and is
|
|
Packit |
f574b8 |
rendered and displayed by Lynx. Restrictions on
|
|
Packit |
f574b8 |
use of lynxcgi and on acceptable paths can be imposed in
|
|
Packit |
f574b8 |
userdefs.h and lynx.cfg, qv.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
This is a Lynxism and should be used only in local documents
|
|
Packit |
f574b8 |
intended solely for Lynx, or for limited local
|
|
Packit |
f574b8 |
testing of CGI scripts without an http server.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
URL:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx recognizes the NcFTP-style ftp URL,
|
|
Packit |
f574b8 |
e.g.,
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ftpHost:fileSpecification
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
for example
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
ftp.gnu.org:/pub/gnu
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
internal URLs:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Lynx uses a variety of private URL schemes
|
|
Packit |
f574b8 |
for communication among its internal modules. They start with
|
|
Packit |
f574b8 |
uppercase letters LYNX by convention, although, as
|
|
Packit |
f574b8 |
input, URL schemes are recognized in a case-insensitive
|
|
Packit |
f574b8 |
manner.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
As you discover what they are, and are tempted to use them
|
|
Packit |
f574b8 |
externally in documents, you should resist that
|
|
Packit |
f574b8 |
temptation:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
There already is too much browser-specific markup
|
|
Packit |
f574b8 |
around...
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
The schemes, or their meanings, may change between
|
|
Packit |
f574b8 |
Lynx versions.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Even if a scheme stays the same, some aspect of its
|
|
Packit |
f574b8 |
behavior may be modified without notice, or the context in
|
|
Packit |
f574b8 |
which it is allowed may change.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If it does not work as expected when used outside of the
|
|
Packit |
f574b8 |
intended purpose, do not expect anyone to "fix" it.
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
For example, tempting though it might be, do not use
|
|
Packit |
f574b8 |
these:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
Return to your <A HREF="LYNXHIST:0">Startfile</A>
|
|
Packit |
f574b8 |
Review your <A HREF="LYNXKEYMAP:">Keymap</A>
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
(No, they will not do any harm. Yes, they work. But do not
|
|
Packit |
f574b8 |
rely on it.)
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
If you must try one, the second is OK from the command
|
|
Packit |
f574b8 |
line:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
lynx LYNXKEYMAP:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
But within Lynx, use the
|
|
Packit |
f574b8 |
“K” keystroke command. Sometimes it may be
|
|
Packit |
f574b8 |
convenient to use a private scheme with
|
|
Packit |
f574b8 |
“g”oto, as in:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
g LYNXMESSAGES:
|
|
Packit |
f574b8 |
g LYNXCOMPILEOPTS:
|
|
Packit |
f574b8 |
g LYNXCFG:
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
|
|
Packit |
f574b8 |
But again, there usually is a way in which those special pages
|
|
Packit |
f574b8 |
are meant to be reached that is more convenient.
|
|
Packit |
f574b8 |
</body>
|
|
Packit |
f574b8 |
</html>
|