Re: LYNX-DEV Re: News: anywhere vs. NNTP: to-server, eh?
David Woolley <email@example.com> Wed, 20 August 1997 07:03 UTC
Received: from cnri by ietf.org id aa02368; 20 Aug 97 3:03 EDT
Received: from services.bunyip.com (services.Bunyip.Com [184.108.40.206]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid DAA19419; Wed, 20 Aug 1997 03:06:45 -0400 (EDT)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id CAA17291 for uri-out; Wed, 20 Aug 1997 02:50:43 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [220.127.116.11]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id CAA17286 for <firstname.lastname@example.org>; Wed, 20 Aug 1997 02:50:40 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id CAA21868 for uri@services; Wed, 20 Aug 1997 02:49:45 -0400 (EDT)
Received: from djwhome.demon.co.uk (djwhome.demon.co.uk [18.104.22.168]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id CAA21865 for <uri@bunyip.COM>; Wed, 20 Aug 1997 02:49:41 -0400 (EDT)
Received: (from david@localhost) by djwhome.demon.co.uk (8.8.6/8.7.3) id WAA28518; Tue, 19 Aug 1997 22:39:39 +0100
From: David Woolley <email@example.com>
Subject: Re: LYNX-DEV Re: News: anywhere vs. NNTP: to-server, eh?
Date: Tue, 19 Aug 1997 22:39:34 +0100 (BST)
Cc: firstname.lastname@example.org, email@example.com
In-Reply-To: <33F87792.825DC165@parc.xerox.com> from "Larry Masinter" at Aug 18, 97 09:25:54 am
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text/plain; charset=US-ASCII
> > What is currently widely deployed is > news:[//host/]newsgroup > > rather than 'nttp:'. So I suggest we just try to write up what people > are using rather than continuing to push on "nntp:". I think this is only people using Netscape browsers. Microsoft Interenet Explorer 3 doesn't understand this particular abuse, and nor do any of caching proxies available from my office (not that I can find a caching proxy that understands nntp: either, but at least the reject it without getting confused). (MSIE 3 tries to launch Microsoft News, which tries for the default news server.) Personally, I think any such interpretation of news:// should be enabled by an option which defaults to disabled, to just make people aware that the URL is broken.
- News: anywhere vs. NNTP: to-server, eh? Al Gilman
- Re: News: anywhere vs. NNTP: to-server, eh? Larry Masinter
- Re: LYNX-DEV Re: News: anywhere vs. NNTP: to-serv… David Woolley