From 6f66219647d92d2af2427d416e00e6f2a8f825dc Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" Date: Sun, 9 Feb 1997 22:44:52 -0500 Subject: snapshot of project "lynx", label v2_6fm_970209 --- lynx_help/lynx_url_support.html | 51 +++++++++++++++++++++++++++++++++++++---- 1 file changed, 47 insertions(+), 4 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 61800f4f..c90550f4 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -14,6 +14,7 @@ ftp | wais | news, nntp, snews | +newspost, newsreply, snewspost, snewsreply | mailto | finger | cso | @@ -296,10 +297,10 @@ hierarchies or sub-hierarchies, e.g.:
(snews same as nntp, but the default port is :563)
This is not in RFC1738 and may not be supported by all other clients. -

For news URLs, Lynx allows you both to reply to the author -of a message via email, and, if news posting has been enabled, to send -a followup message to the newsgroup. Only email replies to the -author are permitted via nntp URLs. +

Lynx allows you both to reply to the author of a news message +via email, and, if news posting has been enabled, to send a followup +message to the newsgroup (see newspost, newsreply, +snewspost, snewsreply).

Lynx converts any strings in news messages which appear to be a URL with a supported scheme into a link for accessing that URL. @@ -317,6 +318,48 @@ are specific to each nntp server, unlike the unique identifiers for news messages.

+

The newspost, newsreply, snewspost, and +snewsreply URLs:

+ +When Lynx receives group listings or articles via news, +nntp or snews 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 :119. +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. + +

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) + +

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 newgroup names +is not supported for these URLs. For newsreply and snewsreply URLs, the +user is offered the option to include the currently displayed document, +which presumeably is a news article with a followup link that +was activated, and if confirmed, each line of that document is prefixed +with a right-angle-bracket. 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 mailto URLs, +with the qualification that they presently are supported only by Lynx. +

+

The mailto URL:

The mailto URL is used to provide links that when activated can be -- cgit 1.4.1-2-gfad0