diff options
| author | Thomas E. Dickey <dickey@invisible-island.net> | 2021-07-02 00:15:34 +0000 |
|---|---|---|
| committer | Thomas E. Dickey <dickey@invisible-island.net> | 2021-07-02 00:15:34 +0000 |
| commit | 35787b45f4cbf08d6e4d913e859a39a4e4369766 (patch) | |
| tree | 01ee977a699ad9f78393fca6bef3888bc707b715 /lynx_help/lynx_url_support.html | |
| parent | 811be0812233351687f2215e264eeb886a2a0060 (diff) | |
| download | lynx-snapshots-35787b45f4cbf08d6e4d913e859a39a4e4369766.tar.gz | |
snapshot of project "lynx", label v2-9-0dev_6l
Diffstat (limited to 'lynx_help/lynx_url_support.html')
| -rw-r--r-- | lynx_help/lynx_url_support.html | 101 |
1 files changed, 56 insertions, 45 deletions
diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html index 78849c23..52ba2fb7 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -1,19 +1,16 @@ -<!-- $LynxId: lynx_url_support.html,v 1.36 2017/04/28 16:47:05 tom Exp $ --> +<!-- $LynxId: lynx_url_support.html,v 1.37 2021/07/01 21:02:17 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> - <html> <head> <meta name="generator" content= - "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - + "HTML Tidy for HTML5 for Linux version 5.6.0"> <title>URL Schemes Supported in Lynx</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> <meta name="description" content= - " Enumerate, describe and provide examples of Lynx's URL support on Unix and VMS. Lynx supports both Web standards and extensions."> - </head> - + "Enumerate, describe and provide examples of Lynx's URL support on Unix and VMS. Lynx supports both Web standards and extensions."> +</head> <body> <blockquote> <p><em>[</em><a href="#http_url">http, https</a> <em>|</em> @@ -31,7 +28,8 @@ <em>|</em> <a href="#internal_url">internal</a><em>]</em></p> </blockquote> - <h1><em>URL Schemes Supported in Lynx</em></h1> + <h1><em>URL Schemes Supported in Lynx</em> + </h1> <p><strong>Lynx</strong> handles a number of URL types, that are enumerated below. For more details about URLs (Uniform Resource @@ -96,6 +94,7 @@ “<em>g</em>”oto entries! Any partial or relative URLs within HTML documents are resolved according to the rules specified in RFC1808 and subsequent IETF drafts.</p> + <hr> <h2><a name="http_url" id="http_url">The <em>http</em> and @@ -103,10 +102,10 @@ <p><strong>Lynx</strong> handles http URLs exactly as specified in RFC1738. The format is:</p> + <pre> <em>http://host:port/path?searchpart#fragment</em> </pre> - <p>where <em>:port</em> is optional and defaults to <em>:80</em>, <em>/path</em> if present is a slash-separated series of symbolic elements, and <em>?searchpart</em> if present is the query for an @@ -130,6 +129,7 @@ Certificate Status Protocol (OCSP) which is an external service. Without this facility, <strong>Lynx</strong> may not warn about websites using revoked SSL certificates.</p> + <hr> <h2><a name="telnet_url" id="telnet_url">The <em>telnet</em>, @@ -139,10 +139,10 @@ <strong>Lynx</strong> spawning a telnet session. <strong>Lynx</strong> implements the complete telnet URL scheme, i.e.:</p> + <pre> <em>telnet://user:password@host:port</em> </pre> - <p>The <em>user</em> and/or <em>:password</em> fields may be omitted, and the <em>@</em> should be omitted if neither is present. The port defaults to <em>:23</em> when omitted in the @@ -157,16 +157,17 @@ for URLs which point to anonymous or other public access accounts, and for most TCP-IP software you will be prompted for a password whether or not one was included in the URL.</p> + <hr> <h2><a name="gopher_url" id="gopher_url">The <em>gopher</em> URL:</a></h2> <p>The gopher URL takes the form:</p> + <pre> <em>gopher://host:port/gopher-path</em> </pre> - <p>where <em>:port</em> is optional and defaults to <em>:70</em>, and the <em>/gopher-path</em> is opaque (not fully equivalent to the slash-separated series of symbolic elements of http paths) as @@ -200,15 +201,15 @@ if the <em>selector</em> begins with <em>GET%20/</em> <strong>Lynx</strong> will convert the gopher URL to an http URL, e.g.:<br></p> + <pre> <em>gopher://www.wfbr.edu:80/hGET%20/</em> </pre> - <p>will become:<br></p> + <pre> <em>http://www.wfbr.edu/</em> </pre> - <p>The port field will be retained if it is not <em>:80</em>, and will default to <em>:70</em> if it was defaulted originally. These conventions were adopted during development of the @@ -216,39 +217,39 @@ offering of links to MIME-capable http servers in the listings returned by gopher servers, but should be considered Lynxisms and UMN Gopherisms.</p> + <hr> - <h2><a name="file_url" id="file_url">The <em>file</em> - URL:</a></h2> + <h2><a name="file_url" id="file_url">The <em>file</em> URL:</a></h2> <p>The file URL is used to retrieve files or generate a directory listing on the local host. The host field can be <em>localhost</em> or a domain name for the local host:<br></p> + <pre> <em>file://localhost/path</em> </pre> - <p>If you do not use <em>localhost</em> or a domain name for the local host, <strong>Lynx</strong> will substitute <em>ftp://</em> for <em>file://</em> and treat it as an ftp URL.</p> <p>The <em>/path</em> is treated as originating at the root, unless you include a tilde (<em>~</em>), e.g.:</p> + <pre> <em>file://localhost/~/foo</em> will be converted to: <em>file://localhost/your/login/directory/foo</em> </pre> - <p>The latter feature is a Lynxism, is done homologously on Unix and VMS, and should be used ONLY in local documents intended for <strong>Lynx</strong>.</p> <p>On VMS, the first element of the path, if not a tilde, is assumed to be a device, e.g.:</p> + <pre> <em>file://localhost/www_root/directory/filename.suffix</em> </pre> - <p>should be used for: <em>www_root:[directory]filename.suffix</em><br> If you are unsure how to specify a file URL in local documents on @@ -256,16 +257,17 @@ directory as the <em>startfile</em> using any spec acceptable to DCL, and then use the <em>showinfo</em> command (<em>=</em>) to see the file URL which <strong>Lynx</strong> created for it.</p> + <hr> <h2><a name="ftp_url" id="ftp_url">The <em>ftp</em> URL:</a></h2> <p>The ftp URL has the general format:</p> + <pre> <em>ftp://host:port/path;type=[D,I, or A]</em> <em>ftp://username@host:port/path;type=[D,I, or A]</em> </pre> - <p>The default port is <em>:21</em> and the default <em>username</em> is <em>anonymous</em>. If <em>username</em> is included, <strong>Lynx</strong> will prompt you for the password. @@ -300,18 +302,18 @@ first element treated as a device rather than file or subdirectory name, begin it with a hex-escaped slash (<em>%2f</em>), e.g.:</p> + <pre> <em>ftp://user@myhost/%2fsys$common/syshlp</em> </pre> - <p>can be used for a listing of sys$common:[syshlp]<br> Also, on VM/CMS ftp servers, if the <em>path</em> string begins with <em>vmsysu%3a</em> it receives special handling as an SFS path, e.g.:</p> + <pre> <em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em> </pre> - <p>For Unix and Unix-emulation ftp servers, RFC1738 is not respected and the lead slash is treated as the root, i.e., the <em>/path</em> is handled equivalently to that in file URLs. The @@ -321,22 +323,23 @@ or have the <em>path</em> string treated as a file or path under the login directory, include a tilde (<em>~</em>) as for <a href= "#file_url">file</a> URLs, e.g.:</p> + <pre> <em>ftp://user@myhost/~</em> </pre> + <hr> - <h2><a name="wais_url" id="wais_url">The <em>wais</em> - URL:</a></h2> + <h2><a name="wais_url" id="wais_url">The <em>wais</em> URL:</a></h2> <p>The wais URL is used to retrieve resources using the Wide Area Information System protocol. The format is:</p> + <pre> <em>wais://host:port/database</em> <em>wais://host:port/database?wais_query</em> <em>wais://host:port/database/wais_type/wais_path</em> </pre> - <p>where <em>:port</em> defaults to <em>:210</em></p> <p>Direct wais support is built into <strong>Lynx</strong> for @@ -349,6 +352,7 @@ the server's reply into a hit list with URLs that include the <em>wais_type</em> and <em>wais_path</em> for retrieving items from the hit list.</p> + <hr> <h2><a name="news_url" id="news_url">The <em>news</em>, @@ -373,6 +377,7 @@ password and username (in that order) separated by a space.</p> <p>The formats are:<br></p> + <pre> <em>news:newsgroup</em> (retrieves list of messages in newsgroup) <em>news:messageID</em> (retrieves the message) @@ -381,7 +386,6 @@ <em>nntp://host:port/messageID</em> <em>nntp://host:port/*</em> </pre> - <p>(snews same as nntp, but the default port is <em>:563</em>)</p> @@ -392,11 +396,11 @@ <p><strong>Lynx</strong> also supports wildcarding via an asterisk for listings of news hierarchies or sub-hierarchies, e.g.:</p> + <pre> <em>news:comp.infosystems.*</em> <em>nntp://host:port/comp.infosystems.*</em> </pre> - <p>(snews same as nntp, but the default port is <em>:563</em>)<br> This is not in RFC1738 and may not be supported by all other @@ -414,18 +418,19 @@ <p><strong>Lynx</strong> also supports the newsgroup and message number URL scheme:<br></p> + <pre> <em>news:newsgroup/startNo-endNo</em> (lists message range in newsgroup) <em>news:newsgroup/messageNo</em> (retrieves the message by number) <em>nntp://host:port/newsgroup/startNo-endNo</em> <em>nntp://host:port/newsgroup/messageNo</em> </pre> - <p>(snews same as nntp, but the default port is <em>:563</em>)<br> Use of this scheme is not recommended, because the message numbers are specific to each nntp server, unlike the unique identifiers for news messages.</p> + <hr> <h2><a name="newspost_url" id="newspost_url">The @@ -448,11 +453,11 @@ servers.</p> <p>The formats are:</p> + <pre> <em>newspost://host:port/newsgroup(s)</em> (post a new message) <em>newsreply://host:port/newsgroup(s)</em> (post a followup message) </pre> - <p>(snewspost and snewsreply have the same formats, but the default port is <em>:563</em>)</p> @@ -477,6 +482,7 @@ attribute values in any HTML document homologously to <a href= "#mailto_url">mailto</a> URLs, with the qualification that they presently are supported only by <strong>Lynx</strong>.</p> + <hr> <h2><a name="mailto_url" id="mailto_url">The <em>mailto</em> @@ -485,10 +491,10 @@ <p>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:</p> + <pre> <em>mailto:user@host</em> </pre> - <p>The description of the mailto URL in RFC1738 has been interpreted by some as allowing only a single recipient, but <strong>Lynx</strong> invented the mailto URL, has always @@ -505,6 +511,7 @@ 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.:</p> + <pre> <em><LINK REV="made" HREF="mailto:me@myhost,her@herhost" TITLE="The Subject"></em> @@ -516,7 +523,6 @@ ... </FORM></em> </pre> - <p>Note that a TITLE attribute for FORM is now included in the HTML specifications. Some clients use a SUBJECT attribute for this purpose in FORM tags, and <strong>Lynx</strong> recognizes @@ -552,15 +558,15 @@ “<em>;</em>” to separate the pairs, so that the content will be readable directly. Otherwise, <strong>Lynx</strong> will mail the content with the default:</p> + <pre> <em>ENCTYPE="application/x-www-form-urlencoded"</em> (“<em>&</em>” separates pairs) </pre> - <p>or:</p> + <pre> <em>ENCTYPE="application/sgml-form-urlencoded"</em> (“<em>;</em>” separates pairs) </pre> - <p>if the latter was indicated.</p> <p>Note that when mailing FORM content <strong>Lynx</strong> @@ -578,6 +584,7 @@ is prefixed with a right-angle-bracket, and the prefixed inclusion should be trimmed by the user to just those passages relevant to the message which will be sent.</p> + <hr> <h2><a name="finger_url" id="finger_url">The <em>finger</em> @@ -588,6 +595,7 @@ by the IETF. The formats supported by <strong>Lynx</strong> therefore include every possibility not inconsistent with RFC1738, including:</p> + <pre> finger://host finger://@host finger://host/ finger://@host/ @@ -599,7 +607,6 @@ finger://host/%2fw%20username[@host] finger://host/username[@host]/w finger://host/w/username </pre> - <p>Activating a finger URL will send a request to the finger server via port 79 on the host specified. You can include <em>:79</em> in the URL, but no other value is allowed. The @@ -616,6 +623,7 @@ <strong>Lynx</strong> will handle such URLs equivalently to overt finger URLs, including creation of links for any strings which appear to be supported URLs.</p> + <hr> <h2><a name="cso_url" id="cso_url">The <em>cso</em> URL:</a></h2> @@ -623,26 +631,26 @@ <p>The cso URL is intended to provide a gateway to CSO/PH (QI) servers. The requests are made on port 105 by default (<em>:105</em>), with the following overt cso URL format:<br></p> + <pre> <em>cso://host</em> </pre> - <p>You also can use a gopher URL format with port 105 and the CSO (<em>2</em>) <em>gophertype</em> specified:</p> + <pre> <em>gopher://host:105/2</em> </pre> - <p><strong>Lynx</strong> will parse the stream returned by the server for the above URLs and create a FORM for submitting additional requests (searches) to the server. Any strings in the reports returned for these requests (searches) which appear to be a URL with a supported scheme will be converted into a link for accessing that URL.</p> + <hr> - <h2><a name="bibp_url" id="bibp_url">The <em>bibp</em> - URL:</a></h2> + <h2><a name="bibp_url" id="bibp_url">The <em>bibp</em> URL:</a></h2> <p><strong>Lynx</strong> provides built-in support for bibliographic protocol (BibP). BibP links are links to published @@ -662,12 +670,12 @@ qualifiers can be used, with the syntax appropriate for a shell running <strong>Lynx</strong> on Unix, or for DCL on VMS, e.g.:</p> + <pre> <em>lynxexec:dir/date/size foo:[blah]</em> (VMS) <em>lynxexec:ls -l /foo/blah</em> (Unix) <em>lynxprog:news</em> </pre> - <p>(Note, however, that restrictions on acceptable commands or utilities may be imposed by the system administrator.)</p> @@ -682,18 +690,18 @@ <p>These are Lynxisms and should be used only in local documents intended solely for <strong>Lynx</strong>.</p> + <hr> - <h2><a name="cgi_url" id="cgi_url">The <em>lynxcgi</em> - URL:</a></h2> + <h2><a name="cgi_url" id="cgi_url">The <em>lynxcgi</em> URL:</a></h2> <p>The lynxcgi URL is implemented only on Unix, can be used as the ACTION for a FORM, and if enabled in your <strong>Lynx</strong> image has the format:</p> + <pre> <em>lynxcgi://localhost/path_to_CGI_script</em> </pre> - <p>where <em>//localhost</em> is optional and always implied; the full path should be specified, as “~” is not recognized; if the script is in the directory @@ -706,6 +714,7 @@ <p>This is a Lynxism and should be used only in local documents intended solely for <strong>Lynx</strong>, or for limited local testing of CGI scripts without an http server.</p> + <hr> <h2><a name="ncftp_url" id="ncftp_url">The <em>NcFTP</em> @@ -713,16 +722,18 @@ <p><strong>Lynx</strong> recognizes the NcFTP-style ftp URL, e.g.,</p> + <pre> <cite>ftpHost</cite>:<cite>fileSpecification</cite> </pre> - <p>for example</p> + <pre> <code> ftp.gnu.org:/pub/gnu </code> </pre> + <hr> <h2><a name="internal_url" id="internal_url">The <em>LYNXfoo</em> @@ -755,30 +766,30 @@ <p>For example, tempting though it might be, do not use these:</p> + <pre> <em>Return to your <A HREF="LYNXHIST:0">Startfile</A></em> <em>Review your <A HREF="LYNXKEYMAP:">Keymap</A></em> </pre> - <p>(No, they will not do any harm. Yes, they work. But do not rely on it.)</p> <p>If you must try one, the second is OK from the command line:<br></p> + <pre> <em>lynx LYNXKEYMAP:</em> </pre> - <p>But within <strong>Lynx</strong>, use the “<em>K</em>” keystroke command. Sometimes it may be convenient to use a private scheme with “<em>g</em>”oto, as in:</p> + <pre> <em>g LYNXMESSAGES:</em> <em>g LYNXCOMPILEOPTS:</em> <em>g LYNXCFG:</em> </pre> - <p>But again, there usually is a way in which those special pages are meant to be reached that is more convenient.</p> </body> |