lynx_url_support.html

一个可用于linux下的命令行音乐播放器

      <em>nntp://host:port/comp.infosystems.*</em>
</pre>
(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.

<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 a <em>followup</em>
message to the newsgroup (see <a href="#newspost">newspost, newsreply,
snewspost, snewsreply</a>).

<p>Lynx converts any strings in news messages which appear to be a URL
with a supported scheme into a link for accessing that URL.

<p>Lynx also supports the newsgroup and message number URL scheme:<BR>
<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>
(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.
<HR>

<H2><a name="newspost_url"
>The <em>newspost</em>, <em>newsreply</em>, <em>snewspost</em>, and
<em>snewsreply</em> URLs:</a></H2>

When Lynx receives group listings or articles via <em>news</em>,
<em>nntp</em> or <em>snews</em> URLs, it also checks whether the
nntp server supports posting from the Lynx user's site, and if so,
includes links for posting new messages to that server, or for posting
followups (replies) to previously posted messages.  RFC1738, and IETF
URL drafts through this release of Lynx, do not include any schemes
for posting to news groups.  Lynx has long supported newspost and
newreply URL schemes for posting new messages or sending followups,
respectively, to standard nntp servers, with default port <em>:119</em>.
Lynx now also supports homologous snewspost and snewsreply URLs for use
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.

<p>The formats are:
<pre>
      <em>newspost://host:port/newsgroup(s)</em>&nbsp;&nbsp;(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>)

<p>If the host field is omitted, it defaults to that pointed to by the
NNTPSERVER configuration or environmental variable.  Inclusion of at
least one newsgroup in the URL is required, and additional groups can
be specified as a comma-separated list.  Wildcarding of newsgroup names
is not supported for these URLs.  For newsreply and snewsreply URLs, if
an external editor has been defined via the <em>Options Menu</em>, the
user is offered an option to include the currently displayed document,
which presumably is a news article with a <em>followup</em> link that
was activated, and if confirmed, each line of that document is prefixed
with a right-angle-bracket.  The user is expected to edit such an inclusion
so that only the passages relevant to the followup message are retained.

<p>These URLs can be used as command line startfiles (in which case, Lynx
will exit after posting the message, and the newreply or snewsreply URLs
degrade to newspost or snewpost URLs, respectively).  They also can be used
as HREF attribute values in any HTML document homologously to <a
href="#mailto">mailto</a> URLs, with the qualification that they presently
are supported only by Lynx.
<HR>

<H2><a name="mailto_url">The <em>mailto</em> URL:</a></H2>

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:
<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 Lynx invented the mailto URL,
has always supported a series of user@host addresses as a comma-separated
list, and still does.  For compatibility with Explorer, Lynx also accepts
a semi-colon-separated list.

<p>For compatibility with Netscape, Lynx parses any
<em>?subject=The%20Subject</em> appended to the URL, trims the URL
at the <em>?</em>, 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.:
<pre>
      <em>&lt;LINK REV="made"
            HREF="mailto:me@myhost,her@herhost" TITLE="The Subject"&gt;</em>

      <em>&lt;A HREF="mailto:user@host" TITLE="The Subject"&gt;...&lt;/A&gt;</em>

      <em>&lt;FORM METHOD="post" ENCTYPE="text/plain"
            ACTION="mailto:WebMaster@host" TITLE="The Subject"&gt;
       ...
      &lt;/FORM&gt;</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 Lynx recognizes that as a synonym for TITLE.

<p>Lynx also will process any <em>to=address(es)</em>,
<em>cc=address(es)</em>, <em>keywords=word_list</em> and/or
<em>body=message</em> fields in <em>?searchpart</em> tack-ons to mailto
URLs.  The <em>to</em> and/or <em>cc</em> values can be single addresses,
or comma- or semi-colon-separated lists of addresses.  All addresses,
and any <em>body</em> values, will be offered for approval by the user
before proceeding with a mailing.   Any other name=value pairs in the
<em>?searchpart</em> will be ignored.  Also, if the mailto URL is the
ACTION for a FORM, any <em>body</em> in a <em>?searchpart</em> tack-on
will be ignored, because the body of the mailing must be constructed
solely from the the FORM's content.  Lynx expects multiple name=value
pairs in a <em>?searchpart</em> tack-on to be separated by ampersands,
as in the original Netscape implementation, and in an equally ill-advised
IETF draft of that implementation (<a
href="ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-03.txt"
>draft-hoffman-mailto-url-03.txt</a>).  These should be represented as
entities (<em>&amp;amp;</em>) in the HTML markup.  This functionality
is generally desired, but the IETF backward compatibility principal
normally would lead to a new scheme being used (e.g., <em>mail:</em>, or
<em>smtp:</em>), rather than breaking <em>mailto:</em> implementations.

<p>If <em>ENCTYPE="text/plain"</em> is specified for a FORM with a mailto
ACTION, Lynx will not hex escape the name=value pairs of the FORM's content,
and will use physical newlines instead of '<em>&amp;</em>' or '<em>;</em>'
to separate the pairs, so that the content will be readable directly.
Otherwise, Lynx will mail the content with the default:
<pre>
      <em>ENCTYPE="application/x-www-form-urlencoded"</em> ('<em >&amp;</em>' separates pairs)
</pre>
or:
<pre>
      <em>ENCTYPE="application/sgml-form-urlencoded"</em> ('<em >;</em>' separates pairs)
</pre>
if the latter was indicated.

<p>Note that when mailing FORM content Lynx wraps any lines longer than 78
characters, to avoid buffer overflows in mail software and to ensure reliable
transmission across gateways.  If the ENCTYPE was not <em>text/plain</em>,
any script which decodes the mailed content should ignore the physical
newlines and recognize only hex escaped newline characters as intended
to be present in the decoded content.

<p>If the mailto URL is not the ACTION for a FORM, and if an external
editor has been defined via the <em>Options Menu</em>, the user is offered
an option to include the currently displayed document.  If this option is
accepted, each line of that document 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.
<HR>

<H2><a name="finger_url">The <em>finger</em> URL:</a></H2>

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
therefore include every possibility not inconsistent with RFC1738,
including:

<pre>
 finger://host                         finger://@host
 finger://host/                        finger://@host/
 finger://host/%2fw                    finger://@host/w
 finger://host/w                       finger://host/w/
 finger://host/username[@host]         finger://username@host
 finger://host/username[@host]/        finger://username@host/
 finger://host/w/username[@host]       finger://username@host/w
 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 <em>/w</em> or <em>/%2fw</em> is used
to request a full report for finger servers which support it, and is not
case sensitive (i.e., can be <em>/W</em> or <em>/%2fW</em>).  Any strings
in the report which appear to be a URL with a supported scheme will be
converted into a link for accessing that URL.

<p>An alternative way to access finger servers is via gopher URLs with
port 79 and the plain text (<em>0</em>) <em>gophertype</em> specified:<BR>
<em>gopher://host:79/0</em><BR>
Lynx will handle such URLs equivalently to overt finger URLs, including
creation of links for any strings which appear to be supported URLs.
<HR>

<H2><a name="cso_url">The <em>cso</em> URL:</a></H2>

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>
<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:
<pre>
      <em>gopher://host:105/2</em>
</pre>

<p>Lynx 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.
<HR>

<H2><a name="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 journal articles,
without a predefined server.  BibP links are intended for resolution
by a local bibhost server (http://bibhost/) if it exists.   Otherwise,
resolution is performed by a document-specified server or a known global
server.

<H2><a name="exec_url">The <em>lynxexec</em> and <em>lynxprog</em> URLs:</a></H2>

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.:
<pre>
      <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.)

<p>You optionally can include <em>//localhost/</em> in the URL, between the
scheme field and the command, but that is always implied.  The lynxexec
and lynxprog URLs differ only in that with lynxexec you are prompted to
enter <em>RETURN</em> before Lynx clears the screen and restores the
previously displayed document, so that you can read any screen output
generated by the spawned command, whereas no such pause is imposed upon exit
from the utility invoked via lynxprog.

<p>These are Lynxisms and should be used only in local documents intended
solely for Lynx.
<HR>

<H2><a name="cgi_url">The <em>lynxcgi</em> URL:</a></H2>

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:
<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.

<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.
<HR>

<H2><a name="ncftp_url">The <em>NcFTP</em> URL:</a></H2>

Lynx recognizes the NcFTP-style ftp URL, e.g.,
<pre>
	<cite>ftpHost</cite>:<cite>fileSpecification</cite>
</pre>
for example
<pre><code>
	ftp.gnu.org:/pub/gnu
</code></pre>
<HR>

<H2><a name="internal_url">The <em>LYNXfoo</em> internal URLs:</a></H2>

Lynx uses a variety of private URL schemes for communication among its
internal modules.  They start with uppercase letters <code>LYNX</code>
by convention, although, as input, URL schemes are recognized in a
case-insensitive manner.
<p>
As you discover what they are, and are tempted to use them externally in
documents, you should <em>resist</em> that temptation:
<UL><LI>There already is too much browser-specific markup around...
<LI>The schemes, or their meanings, may change between Lynx versions.
<LI>Even if a scheme stays the same, some aspect of its behavior may
    be modified without notice, or the context in which it is allowed
    may change.
<LI>If it doesn't work as expected when used outside of the intended
    purpose, don't expect anyone to "fix" it.
</UL>

<p>For example, tempting though it might be, do not use these:
<pre>
      <em>Return to your &lt;A HREF="LYNXHIST:0"&gt;Startfile&lt;/A&gt;</em>
      <em>Review your &lt;A HREF="LYNXKEYMAP:"&gt;Keymap&lt;/A&gt;</em>
</pre>
(No, they won't do any harm.  Yes, they work.  But don't rely on it.)

<p>If you must try one, the second is OK from the command line:<BR>
<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>
      <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.
</BODY>
</HTML>