From f78e27712a4f44dbdf3c1532c3d1958989bf40a5 Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" Date: Sat, 6 Oct 2001 22:20:25 -0400 Subject: snapshot of project "lynx", label v2-8-5dev_3 --- lynx_help/lynx_url_support.html | 73 ++++++++++++++++++++++++----------------- 1 file changed, 43 insertions(+), 30 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 bee82050..ac2ccbb9 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -7,21 +7,22 @@
-[http, https | -telnet, tn3270, rlogin | -gopher | -file | -ftp | -wais | -news, nntp, snews | -newspost, newsreply, snewspost, snewsreply | -mailto | -finger | -cso | -bibp | -lynxexec, lynxprog | -lynxcgi| -internal] +[http, https | +telnet, tn3270, rlogin | +gopher | +file | +ftp | +wais | +news, nntp, snews | +newspost, newsreply, snewspost, snewsreply | +mailto | +finger | +cso | +bibp | +lynxexec, lynxprog | +lynxcgi| +NcFTP | +internal]

URL Schemes Supported in Lynx

@@ -74,7 +75,7 @@ Any partial or relative URLs within HTML documents are resolved according to the rules specified in RFC1808 and subsequent IETF drafts.
-

The http and https URLs:

+

The http and https URLs:

Lynx handles http URLs exactly as specified in RFC1738. The format is: @@ -99,7 +100,7 @@ and associated red tape pose severe impediments to inclusion of this support 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 @@ -123,7 +124,7 @@ for most TCP-IP software you will be prompted for a password whether or not one was included in the URL.
-

The gopher URL:

+

The gopher URL:

The gopher URL takes the form:
@@ -172,7 +173,7 @@ listings returned by gopher servers, but should be considered Lynxisms
 and UMN Gopherisms.
 
-

The file URL:

+

The file URL:

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 @@ -206,7 +207,7 @@ use the showinfo command (=) to see the file URL which Lynx created for it.
-

The ftp URL:

+

The ftp URL:

The ftp URL has the general format:
@@ -267,7 +268,7 @@ tilde (~) as for file URLs, e.g.:
 

-

The wais URL:

+

The wais URL:

The wais URL is used to retrieve resources using the Wide Area Information System protocol. The format is: @@ -289,7 +290,7 @@ convert the server's reply into a hit list with URLs that include the the hit list.
-

The news, nntp, and snews URLs:

The news and nntp URLs are handled by Lynx as specified in RFC1738, but @@ -349,7 +350,7 @@ are specific to each nntp server, unlike the unique identifiers for news messages.
-

The newspost, newsreply, snewspost, and snewsreply URLs:

@@ -395,7 +396,7 @@ href="#mailto">mailto URLs, with the qualification that they presently are supported only by Lynx.
-

The mailto URL:

+

The mailto URL:

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 @@ -483,7 +484,7 @@ and the prefixed inclusion should be trimmed by the user to just those passages relevant to the message which will be sent.
-

The finger URL:

+

The finger URL:

Lynx has full support for the finger protocol, but a format for finger URLs has not yet been adopted by the IETF. The formats supported by Lynx @@ -517,7 +518,7 @@ Lynx will handle such URLs equivalently to overt finger URLs, including creation of links for any strings which appear to be supported URLs.
-

The cso URL:

+

The cso URL:

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 @@ -539,7 +540,7 @@ to the server. Any strings in the reports returned for these requests converted into a link for accessing that URL.
-

The bibp URL:

+

The bibp URL:

Lynx provides built-in support for bibliographic protocol (BibP). BibP links are links to published works such as books or journal articles, @@ -548,7 +549,7 @@ by a local bibhost server (http://bibhost/) if it exists. Otherwise, resolution is performed by a document-specified server or a known global server. -

The lynxexec and lynxprog URLs:

+

The lynxexec and lynxprog URLs:

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 @@ -575,7 +576,7 @@ from the utility invoked via lynxprog. solely for Lynx.
-

The lynxcgi URL:

+

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: @@ -602,7 +603,19 @@ more efficient and comprehensive than any code which might be incorporated within Lynx.
-

The LYNXfoo internal URLs:

+

The NcFTP URL:

+ +Lynx recognizes the NcFTP-style ftp URL, e.g., +
+	ftpHost:fileSpecification
+
+for example +

+	ftp.gnu.org:/pub/gnu
+
+
+ +

The LYNXfoo internal URLs:

Lynx uses a variety of private URL schemes for communication among its internal modules. They start with uppercase letters LYNX -- cgit 1.4.1-2-gfad0