From 95586cc28c61df18b7a2cd2a9b3ee4c4c83aa583 Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" Date: Wed, 29 Sep 1999 11:47:35 -0400 Subject: snapshot of project "lynx", label v2-8-3dev_10 --- lynx_help/lynx_url_support.html | 213 +++++++++++++++++++++++----------------- 1 file changed, 123 insertions(+), 90 deletions(-) (limited to 'lynx_help/lynx_url_support.html') diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html index 759e32f2..80d6bf1f 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -76,8 +76,10 @@ according to the rules specified in RFC1808 and subsequent IETF drafts.

The http and https URLs:

Lynx handles http URLs exactly as specified in RFC1738. The format -is:
-http://host:port/path?searchpart#fragment
+is: +
+      http://host:port/path?searchpart#fragment
+
where :port is optional and defaults to :80, /path if present is a slash-separated series of symbolic elements, and ?searchpart if present is the query for an ISINDEX @@ -100,8 +102,10 @@ in the general distributions of freeware WWW clients such as Lynx. Sorry. >The telnet, tn3270, and rlogin URLs: A telnet URL generally results in Lynx spawning a telnet -session. Lynx implements the complete telnet URL scheme, i.e.:
-telnet://user:password@host:port +session. Lynx implements the complete telnet URL scheme, i.e.: +
+      telnet://user:password@host:port
+

The user and/or :password fields may be omitted, and the @ should be omitted if neither is present. The port defaults @@ -120,8 +124,10 @@ or not one was included in the URL.

The gopher URL:

-The gopher URL takes the form:
-gopher://host:port/gopher-path
+The gopher URL takes the form: +
+      gopher://host:port/gopher-path
+
where :port is optional and defaults to :70, and the /gopher-path is opaque (not fully equivalent to the slash-separated series of symbolic elements of http paths) as explained @@ -150,9 +156,13 @@ but other WWW clients may mishandle it.

For the gophertype which signifies HTML (h), if the selector begins with GET%20/ Lynx will convert the gopher URL to an http URL, e.g.:
-gopher://www.wfbr.edu:80/hGET%20/
+

+gopher://www.wfbr.edu:80/hGET%20/
+
will become:
-http://www.wfbr.edu/
+
+http://www.wfbr.edu/
+
The port field will be retained if it is not :80, and will default to :70 if it was defaulted originally. These conventions were adopted during development of the University of Minnesota gopher software @@ -166,23 +176,27 @@ and UMN Gopherisms. The file URL is used to retrieve files or generate a directory listing on the local host. The host field can be localhost or a domain name for the local host:
-file://localhost/path
+
+file://localhost/path
+
If you do not use localhost or a domain name for the local host, Lynx will substitute ftp:// for file:// and treat it as an ftp URL.

The /path is treated as originating at the root, unless -you include a tilde (~), e.g.:
-file://localhost/~/foo -will be converted to:
-file://localhost/your/login/directory/foo
+you include a tilde (~), e.g.: +

+      file://localhost/~/foo   will be converted to:
+      file://localhost/your/login/directory/foo
+
The latter feature is a Lynxism, is done homologously on Unix and VMS, and should be used ONLY in local documents intended for Lynx.

On VMS, the first element of the path, if not a tilde, is assumed to -be a device, e.g.:
-file://localhost/www_root/directory/filename.suffix
+be a device, e.g.: +

+      file://localhost/www_root/directory/filename.suffix
+
should be used for: www_root:[directory]filename.suffix
If you are unsure how to specify a file URL in local documents on VMS, invoke Lynx with the desired file or directory as the @@ -193,9 +207,10 @@ URL which Lynx created for it.

The ftp URL:

-The ftp URL has the general format:
-ftp://username:password@host:port/path;type=[D,I, or A]
+The ftp URL has the general format: +
+      ftp://username:password@host:port/path;type=[D,I, or A]
+

The default port is :21 and the default username is anonymous. If username is included but not @@ -221,12 +236,16 @@ string if present is treated as in or under the login directory. For VMS ftp servers, if you wish to have the first element treated as a device rather than file or subdirectory name, begin it with a hex-escaped slash (%2f), e.g.:
-ftp://user@myhost/%2fsys$common/syshlp
+

+ftp://user@myhost/%2fsys$common/syshlp
+
can be used for a listing of sys$common:[syshlp]
Also, on VM/CMS ftp servers, if the path string begins with vmsysu%3a it receives special handling as an SFS -path, e.g.:
-ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare +path, e.g.: +
+      ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare
+

For Unix and Unix-emulation ftp servers, RFC1738 is not respected and the lead slash is treated as the root, i.e., the /path is @@ -235,17 +254,21 @@ irrelevant for anonymous ftp, but matters when using ftp for non-anonymous accounts. If you are using ftp with a Unix server and do wish to get a listing of the login directory or have the path string treated as a file or path under the login directory, include a -tilde (~) as for file URLs, e.g.:
-ftp://user@myhost/~ +tilde (~) as for file URLs, e.g.: +

+      ftp://user@myhost/~
+

The wais URL:

The wais URL is used to retrieve resources using the Wide Area Information -System protocol. The format is:
-wais://host:port/database
-wais://host:port/database?wais_query
-wais://host:port/database/wais_type/wais_path
+System protocol. The format is: +
+      wais://host:port/database
+      wais://host:port/database?wais_query
+      wais://host:port/database/wais_type/wais_path
+
where :port defaults to :210

Direct wais support is built into Lynx for VMS, and can be compiled @@ -275,15 +298,14 @@ but cannot be included in the general distribution (sorry, see http and https).

The formats are:
-news:newsgroup (retrieves list of messages in newsgroup)
-news:messageID (retrieves the message)
-news:* (retrieves list of all available newsgroups)
-nntp://host:port/newsgroup
-nntp://host:port/messageID
-nntp://host:port/*
+

+      news:newsgroup (retrieves list of messages in newsgroup)
+      news:messageID (retrieves the message)
+      news:* (retrieves list of all available newsgroups)
+      nntp://host:port/newsgroup
+      nntp://host:port/messageID
+      nntp://host:port/*
+
(snews same as nntp, but the default port is :563)

The messageID is the message's unique identifier, consisting @@ -291,9 +313,11 @@ of an identification string and the host of origin for the message (ident_string@origin_host).

Lynx also supports wildcarding via an asterisk for listings of news -hierarchies or sub-hierarchies, e.g.:
-news:comp.infosystems.*
-nntp://host:port/comp.infosystems.*
+hierarchies or sub-hierarchies, e.g.: +

+      news:comp.infosystems.*
+      nntp://host:port/comp.infosystems.*
+
(snews same as nntp, but the default port is :563)
This is not in RFC1738 and may not be supported by all other clients. @@ -306,12 +330,12 @@ snewspost, snewsreply). with a supported scheme into a link for accessing that URL.

Lynx also supports the newsgroup and message number URL scheme:
-news:newsgroup/startNo-endNo (lists message range in newsgroup)
-news:newsgroup/messageNo (retrieves the message by number)
-nntp://host:port/newsgroup/startNo-endNo
-nntp://host:port/newsgroup/messageNo
+

+      news:newsgroup/startNo-endNo (lists message range in newsgroup)
+      news:newsgroup/messageNo     (retrieves the message by number)
+      nntp://host:port/newsgroup/startNo-endNo
+      nntp://host:port/newsgroup/messageNo
+
(snews same as nntp, but the default port is :563)
Use of this scheme is not recommended, because the message numbers are specific to each nntp server, unlike the unique identifiers for @@ -336,11 +360,11 @@ with SSL capable nntp servers, but the latter requires patches for built in SSL support, or use of a daemon which handles the secure communications on behalf of Lynx. -

The formats are:
-newspost://host:port/newsgroup(s)  (post a new message)
-newsreply://host:port/newsgroup(s) (post a followup message)
+

The formats are: +

+      newspost://host:port/newsgroup(s)  (post a new message)
+      newsreply://host:port/newsgroup(s) (post a followup message)
+
(snewspost and snewsreply have the same formats, but the default port is :563) @@ -368,8 +392,10 @@ are supported only by Lynx. The mailto URL is used to provide links that when activated can be used to send a comment or the content of a FORM to an Internet email -address (user@host). The format is:
-mailto:user@host +address (user@host). The format is: +
+      mailto:user@host
+

The description of the mailto URL in RFC1738 has been interpreted by some as allowing only a single recipient, but Lynx invented the mailto URL, @@ -383,18 +409,18 @@ at the ?, and uses the value as the default Subject: for the message or FORM content mailing. This is not recommended practice. The preferred way to indicate the default Subject: for a LINK or Anchor with a mailto HREF, or a FORM with a mailto ACTION, is via a TITLE -attribute with the subject string as its value, e.g.:
-<LINK REV="made"
-HREF="mailto:me@myhost,her@herhost" TITLE="The Subject"> +attribute with the subject string as its value, e.g.: +

+      <LINK REV="made"
+            HREF="mailto:me@myhost,her@herhost" TITLE="The Subject">
 
-
<A
-HREF="mailto:user@host" TITLE="The Subject">...</A>
+      <A HREF="mailto:user@host" TITLE="The Subject">...</A>
 
-
<FORM METHOD="post"
-ENCTYPE="text/plain"

-ACTION="mailto:WebMaster@host" TITLE="The Subject">

-...

-</FORM>
+      <FORM METHOD="post" ENCTYPE="text/plain"
+            ACTION="mailto:WebMaster@host" TITLE="The Subject">
+       ...
+      </FORM>
+

Note that a TITLE attribute for FORM is now included in the HTML specifications. Some clients use a SUBJECT attribute for this purpose @@ -425,14 +451,14 @@ normally would lead to a new scheme being used (e.g., mail:, or ACTION, Lynx will not hex escape the name=value pairs of the FORM's content, and will use physical newlines instead of '&' or ';' to separate the pairs, so that the content will be readable directly. -Otherwise, Lynx will mail the content with the default:
-ENCTYPE="application/x-www-form-urlencoded" ('&' separates pairs)
-or:
-ENCTYPE="application/sgml-form-urlencoded" (';' separates pairs)
+Otherwise, Lynx will mail the content with the default: +

+      ENCTYPE="application/x-www-form-urlencoded" ('&' separates pairs)
+
+or: +
+      ENCTYPE="application/sgml-form-urlencoded" (';' separates pairs)
+
if the latter was indicated.

Note that when mailing FORM content Lynx wraps any lines longer than 78 @@ -489,11 +515,15 @@ creation of links for any strings which appear to be supported URLs. The cso URL is intended to provide a gateway to CSO/PH (QI) servers. The requests are made on port 105 by default (:105), with the following overt cso URL format:
-cso://host
+

+cso://host
+

You also can use a gopher URL format with port 105 and the CSO -(2) gophertype specified:
-gopher://host:105/2 +(2) gophertype specified: +

+      gopher://host:105/2
+

Lynx will parse the stream returned by the server for the above URLs and create a FORM for submitting additional requests (searches) @@ -508,12 +538,12 @@ If execution of spawned commands has been enabled in your Lynx image, the lynxexec and lynxprog URLs can be used to execute arbitrary system commands or invoke system utilities. Any system command and associated switches or qualifiers can be used, with the syntax appropriate for a shell running -Lynx on Unix, or for DCL on VMS, e.g.:
-lynxexec:dir/date/size foo:[blah] (VMS)
-lynxexec:ls -l /foo/blah (Unix)
-lynxprog:news
+Lynx on Unix, or for DCL on VMS, e.g.: +

+      lynxexec:dir/date/size foo:[blah] (VMS)
+      lynxexec:ls -l /foo/blah          (Unix)
+      lynxprog:news
+
(Note, however, that restrictions on acceptable commands or utilities may be imposed by the system administrator.) @@ -532,10 +562,11 @@ solely for Lynx.

The lynxcgi URL:

The lynxcgi URL is implemented only on Unix, can be used as the -ACTION for a FORM, and if enabled in your Lynx image has the format:
-ly -nxcgi://localhost/path_to_CGI_script
-where //localhost/ is optional and always implied. +ACTION for a FORM, and if enabled in your Lynx image has the format: +
+      lynxcgi://localhost/path_to_CGI_script
+
+where //localhost/ is optional and always implied. The output of the script should be text/html and is rendered and displayed by Lynx. (Note that restrictions on acceptable paths can be imposed by the system administrator.) @@ -559,15 +590,17 @@ objects for communication among its display modules. If you discover what they are, and are tempted to use them externally in documents, find the self-restraint to resist that temptation!!! -

For example, tempting though it might be, do not use these:
-Return to your <A HREF="LYNXHIST:0">Startfile</A>
-Review your <A HREF="LYNXKEYMAP:">Keymap</A>
+

For example, tempting though it might be, do not use these: +

+      Return to your <A HREF="LYNXHIST:0">Startfile</A>
+      Review your <A HREF="LYNXKEYMAP:">Keymap</A>
+
(Yes, they'll work. No, they won't do any harm. But...)

If you must try one, the second is OK from the command line:
-lynx LYNXKEYMAP:
+

+      lynx LYNXKEYMAP:
+
But within Lynx, use the 'K' keystroke command. -- cgit 1.4.1-2-gfad0