diff options
| author | Thomas E. Dickey <dickey@invisible-island.net> | 2013-05-22 00:57:45 -0400 |
|---|---|---|
| committer | Thomas E. Dickey <dickey@invisible-island.net> | 2013-05-22 00:57:45 -0400 |
| commit | f7f5657f1e38597bf3b301d56aa5368c12979524 (patch) | |
| tree | fbf19ded0515323932f397676e33637117071f48 /lynx_help/lynx_url_support.html | |
| parent | e294ae2634858bab2dccda56a4a205a979eab96a (diff) | |
| download | lynx-snapshots-f7f5657f1e38597bf3b301d56aa5368c12979524.tar.gz | |
snapshot of project "lynx", label v2-8-7dev_15f
Diffstat (limited to 'lynx_help/lynx_url_support.html')
| -rw-r--r-- | lynx_help/lynx_url_support.html | 250 |
1 files changed, 152 insertions, 98 deletions
diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html index 390c0153..cc5a65bb 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -1,10 +1,10 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> -<!-- $LynxId: lynx_url_support.html,v 1.30 2012/01/31 10:52:00 tom Exp $ --> +<!-- $LynxId: lynx_url_support.html,v 1.31 2013/05/21 10:50:42 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> <head> <meta name="generator" content= - "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> <title>URL Schemes Supported in Lynx</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> @@ -14,7 +14,7 @@ <body> <blockquote> - <em>[</em><a href="#http_url">http, https</a> <em>|</em> + <p><em>[</em><a href="#http_url">http, https</a> <em>|</em> <a href="#telnet_url">telnet, tn3270, rlogin</a> <em>|</em> <a href="#gopher_url">gopher</a> <em>|</em> <a href= "#file_url">file</a> <em>|</em> <a href="#ftp_url">ftp</a> @@ -26,7 +26,7 @@ <em>|</em> <a href="#bibp_url">bibp</a> <em>|</em> <a href= "#exec_url">lynxexec, lynxprog</a> <em>|</em> <a href= "#cgi_url">lynxcgi</a><em>|</em> <a href="#ncftp_url">NcFTP</a> - <em>|</em> <a href="#internal_url">internal</a><em>]</em> + <em>|</em> <a href="#internal_url">internal</a><em>]</em></p> </blockquote> <h1><em>URL Schemes Supported in Lynx</em></h1> @@ -54,7 +54,9 @@ <li><a href= "ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt</a></li> - </ul>and in subsequent drafts of the <em>IETF</em>: + </ul> + + <p>and in subsequent drafts of the <em>IETF</em>:</p> <ul> <li><a href="http://www.ics.uci.edu/pub/ietf/uri/">Uniform @@ -93,31 +95,32 @@ RFC1808 and subsequent IETF drafts.</p> <hr> - <h2><a name="http_url">The <em>http</em> and <em>https</em> - URLs:</a></h2> + <h2><a name="http_url" id="http_url">The <em>http</em> and + <em>https</em> URLs:</a></h2> <p>Lynx handles http URLs exactly as specified in RFC1738. The format is:</p> <pre> <em>http://host:port/path?searchpart#fragment</em> -</pre>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 ISINDEX search or the content of a FORM with -METHOD="GET". The <em>#fragment</em> field if present indicates a -location in the document to seek for display, based on a NAME-ed -anchor or an ID attribute within the document, and is technically -an instruction rather than part of the URL. Lynx will treat ID -attributes as NAME-ed anchors for all tags in the BODY of a -document which can correspond to positions in the rendering of the -document. +</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 + ISINDEX search or the content of a FORM with METHOD="GET". The + <em>#fragment</em> field if present indicates a location in the + document to seek for display, based on a NAME-ed anchor or an ID + attribute within the document, and is technically an instruction + rather than part of the URL. Lynx will treat ID attributes as + NAME-ed anchors for all tags in the BODY of a document which can + correspond to positions in the rendering of the document.</p> <p>The https URL has the same format, but the default port is <em>:443</em>.</p> <hr> - <h2><a name="telnet_url">The <em>telnet</em>, <em>tn3270</em>, - and <em>rlogin</em> URLs:</a></h2> + <h2><a name="telnet_url" id="telnet_url">The <em>telnet</em>, + <em>tn3270</em>, and <em>rlogin</em> URLs:</a></h2> <p>A <em>telnet</em> URL generally results in Lynx spawning a telnet session. Lynx implements the complete telnet URL scheme, @@ -142,23 +145,27 @@ document. password whether or not one was included in the URL.</p> <hr> - <h2><a name="gopher_url">The <em>gopher</em> URL:</a></h2> + <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>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 explained in RFC1738. Typically, the gopher-path -consists of a <a href= -"keystrokes/gopher_types_help.html"><em>gophertype</em></a> -indicating the file or service type (e.g., <em>0</em> or <em>I</em> -for plain text or an image, respectively, <em>7</em> for a search, -or <em>1</em> for a directory), followed by a platform-specific -<em>selector</em>. Any reserved characters in the selector should -be hex escaped (<em>%hh</em>), including slashes, although hex -escaping of slashes is not required by Lynx in gopher URLs. +</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 + explained in RFC1738. Typically, the gopher-path consists of a + <a href= + "keystrokes/gopher_types_help.html"><em>gophertype</em></a> + indicating the file or service type (e.g., <em>0</em> or + <em>I</em> for plain text or an image, respectively, <em>7</em> + for a search, or <em>1</em> for a directory), followed by a + platform-specific <em>selector</em>. Any reserved characters in + the selector should be hex escaped (<em>%hh</em>), including + slashes, although hex escaping of slashes is not required by Lynx + in gopher URLs.</p> <p>Lynx does not overtly support the gopher+ protocol, and does not represent itself as gopher+ capable when communicating with @@ -179,51 +186,63 @@ escaping of slashes is not required by Lynx in gopher URLs. convert the gopher URL to an http URL, e.g.:<br></p> <pre> <em>gopher://www.wfbr.edu:80/hGET%20/</em> -</pre>will become:<br> +</pre> + + <p>will become:<br></p> <pre> <em>http://www.wfbr.edu/</em> -</pre>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 University -of Minnesota gopher software to facilitate the offering of links to -MIME-capable http servers in the listings returned by gopher -servers, but should be considered Lynxisms and UMN Gopherisms. +</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 + University of Minnesota gopher software to facilitate the + 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">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>If you do not use <em>localhost</em> or a domain name for the -local host, Lynx will substitute <em>ftp://</em> for -<em>file://</em> and treat it as an ftp URL. +</pre> + + <p>If you do not use <em>localhost</em> or a domain name for the + local host, Lynx 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>The latter feature is a Lynxism, is done homologously on Unix -and VMS, and should be used ONLY in local documents intended for -Lynx. +</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 + Lynx.</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>should be used for: -<em>www_root:[directory]filename.suffix</em><br> +</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 VMS, invoke Lynx with the desired file or 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 Lynx created for it. + which Lynx created for it.</p> <hr> - <h2><a name="ftp_url">The <em>ftp</em> URL:</a></h2> + <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> @@ -264,10 +283,12 @@ Lynx. (<em>%2f</em>), e.g.:</p> <pre> <em>ftp://user@myhost/%2fsys$common/syshlp</em> -</pre>can be used for a listing of sys$common:[syshlp]<br> +</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.: + path, e.g.:</p> <pre> <em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em> </pre> @@ -286,7 +307,8 @@ Lynx. </pre> <hr> - <h2><a name="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> @@ -294,7 +316,9 @@ Lynx. <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>where <em>:port</em> defaults to <em>:210</em> +</pre> + + <p>where <em>:port</em> defaults to <em>:210</em></p> <p>Direct wais support is built into Lynx for VMS, and can be compiled into Lynx on Unix.</p> @@ -308,8 +332,8 @@ Lynx. from the hit list.</p> <hr> - <h2><a name="news_url">The <em>news</em>, <em>nntp</em>, and - <em>snews</em> URLs:</a></h2> + <h2><a name="news_url" id="news_url">The <em>news</em>, + <em>nntp</em>, and <em>snews</em> URLs:</a></h2> <p>The news and nntp URLs are handled by Lynx as specified in RFC1738, but for compatibility with other clients, Lynx allows @@ -336,7 +360,10 @@ Lynx. <em>nntp://host:port/newsgroup</em> <em>nntp://host:port/messageID</em> <em>nntp://host:port/*</em> -</pre>(snews same as nntp, but the default port is <em>:563</em>) +</pre> + + <p>(snews same as nntp, but the default port is + <em>:563</em>)</p> <p>The <em>messageID</em> is the message's unique identifier, consisting of an identification string and the host of origin for @@ -347,10 +374,12 @@ Lynx. <pre> <em>news:comp.infosystems.*</em> <em>nntp://host:port/comp.infosystems.*</em> -</pre>(snews same as nntp, but the default port is -<em>:563</em>)<br> +</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 - clients. + clients.</p> <p>Lynx allows you both to <em>reply</em> to the author of a news message via email, and, if news posting has been enabled, to send @@ -369,16 +398,18 @@ Lynx. <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>(snews same as nntp, but the default port is -<em>:563</em>)<br> +</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. + identifiers for news messages.</p> <hr> - <h2><a name="newspost_url">The <em>newspost</em>, - <em>newsreply</em>, <em>snewspost</em>, and <em>snewsreply</em> - URLs:</a></h2> + <h2><a name="newspost_url" id="newspost_url">The + <em>newspost</em>, <em>newsreply</em>, <em>snewspost</em>, and + <em>snewsreply</em> URLs:</a></h2> <p>When Lynx receives group listings or articles via <em>news</em>, <em>nntp</em> or <em>snews</em> URLs, it also @@ -397,8 +428,10 @@ Lynx. <pre> <em>newspost://host:port/newsgroup(s)</em> (post a new message) <em>newsreply://host:port/newsgroup(s)</em> (post a followup message) -</pre>(snewspost and snewsreply have the same formats, but the -default port is <em>:563</em>) +</pre> + + <p>(snewspost and snewsreply have the same formats, but the + default port is <em>:563</em>)</p> <p>If the host field is omitted, it defaults to that pointed to by the NNTPSERVER configuration or environmental variable. @@ -423,7 +456,8 @@ default port is <em>:563</em>) presently are supported only by Lynx.</p> <hr> - <h2><a name="mailto_url">The <em>mailto</em> URL:</a></h2> + <h2><a name="mailto_url" id="mailto_url">The <em>mailto</em> + URL:</a></h2> <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 @@ -495,10 +529,14 @@ default port is <em>:563</em>) the content with the default:</p> <pre> <em>ENCTYPE="application/x-www-form-urlencoded"</em> ('<em>&</em>' separates pairs) -</pre>or: +</pre> + + <p>or:</p> <pre> <em>ENCTYPE="application/sgml-form-urlencoded"</em> ('<em>;</em>' separates pairs) -</pre>if the latter was indicated. +</pre> + + <p>if the latter was indicated.</p> <p>Note that when mailing FORM content Lynx wraps any lines longer than 78 characters, to avoid buffer overflows in mail @@ -517,7 +555,8 @@ default port is <em>:563</em>) relevant to the message which will be sent.</p> <hr> - <h2><a name="finger_url">The <em>finger</em> URL:</a></h2> + <h2><a name="finger_url" id="finger_url">The <em>finger</em> + URL:</a></h2> <p>Lynx has full support for the finger protocol, but a format for finger URLs has not yet been adopted by the IETF. The formats @@ -553,7 +592,7 @@ default port is <em>:563</em>) supported URLs.</p> <hr> - <h2><a name="cso_url">The <em>cso</em> URL:</a></h2> + <h2><a name="cso_url" id="cso_url">The <em>cso</em> URL:</a></h2> <p>The cso URL is intended to provide a gateway to CSO/PH (QI) servers. The requests are made on port 105 by default @@ -576,7 +615,8 @@ default port is <em>:563</em>) URL.</p> <hr> - <h2><a name="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>Lynx provides built-in support for bibliographic protocol (BibP). BibP links are links to published works such as books or @@ -586,7 +626,7 @@ default port is <em>:563</em>) performed by a document-specified server or a known global server.</p> - <h2><a name="exec_url">The <em>lynxexec</em> and + <h2><a name="exec_url" id="exec_url">The <em>lynxexec</em> and <em>lynxprog</em> URLs:</a></h2> <p>If execution of spawned commands has been enabled in your Lynx @@ -599,8 +639,10 @@ default port is <em>:563</em>) <em>lynxexec:dir/date/size foo:[blah]</em> (VMS) <em>lynxexec:ls -l /foo/blah</em> (Unix) <em>lynxprog:news</em> -</pre>(Note, however, that restrictions on acceptable commands or -utilities may be imposed by the system administrator.) +</pre> + + <p>(Note, however, that restrictions on acceptable commands or + utilities may be imposed by the system administrator.)</p> <p>You optionally can include <em>//localhost/</em> in the URL, between the scheme field and the command, but that is always @@ -615,32 +657,38 @@ utilities may be imposed by the system administrator.) intended solely for Lynx.</p> <hr> - <h2><a name="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 Lynx image has the format:</p> <pre> <em>lynxcgi://localhost/path_to_CGI_script</em> -</pre>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 Lynx was started from, the simple file -name is adequate. The output of the script should be text/html and -is rendered and displayed by Lynx. Restrictions on use of lynxcgi -and on acceptable paths can be imposed in <em>userdefs.h</em> and -<em>lynx.cfg</em>, qv. +</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 Lynx was started from, the simple file + name is adequate. The output of the script should be text/html + and is rendered and displayed by Lynx. Restrictions on use of + lynxcgi and on acceptable paths can be imposed in + <em>userdefs.h</em> and <em>lynx.cfg</em>, qv.</p> <p>This is a Lynxism and should be used only in local documents intended solely for Lynx, or for limited local testing of CGI scripts without an http server.</p> <hr> - <h2><a name="ncftp_url">The <em>NcFTP</em> URL:</a></h2> + <h2><a name="ncftp_url" id="ncftp_url">The <em>NcFTP</em> + URL:</a></h2> <p>Lynx recognizes the NcFTP-style ftp URL, e.g.,</p> <pre> <cite>ftpHost</cite>:<cite>fileSpecification</cite> -</pre>for example +</pre> + + <p>for example</p> <pre> <code> ftp.gnu.org:/pub/gnu @@ -648,8 +696,8 @@ and on acceptable paths can be imposed in <em>userdefs.h</em> and </pre> <hr> - <h2><a name="internal_url">The <em>LYNXfoo</em> internal - URLs:</a></h2> + <h2><a name="internal_url" id="internal_url">The <em>LYNXfoo</em> + internal URLs:</a></h2> <p>Lynx uses a variety of private URL schemes for communication among its internal modules. They start with uppercase letters @@ -680,21 +728,27 @@ and on acceptable paths can be imposed in <em>userdefs.h</em> and <pre> <em>Return to your <A HREF="LYNXHIST:0">Startfile</A></em> <em>Review your <A HREF="LYNXKEYMAP:">Keymap</A></em> -</pre>(No, they won't do any harm. Yes, they work. But don't rely -on it.) +</pre> + + <p>(No, they won't do any harm. Yes, they work. But don't 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>But within Lynx, use the '<em>K</em>' keystroke command. -Sometimes it may be convenient to use a private scheme with -'<em>g</em>'oto, as in: +</pre> + + <p>But within Lynx, 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>But again, there usually is a way in which those special -pages are meant to be reached that is more convenient. +</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> </html> |