From owner-freebsd-hackers Sun Sep 2 18:20:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blueyonder.co.uk (pcow034o.blueyonder.co.uk [195.188.53.122]) by hub.freebsd.org (Postfix) with ESMTP id 3A51837B408 for ; Sun, 2 Sep 2001 18:20:18 -0700 (PDT) Received: from mail.yahoo.com ([62.30.72.42]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 3 Sep 2001 02:20:30 +0100 Received: (from steve@localhost) by mail.yahoo.com (8.11.3/8.11.3) id f831JkD00504; Mon, 3 Sep 2001 02:19:46 +0100 (BST) (envelope-from steve) Date: Mon, 3 Sep 2001 02:19:46 +0100 From: Steve Roome To: "David O'Brien" Cc: Keith Stevenson , Leo Bicknell , freebsd-hackers@freebsd.org Subject: Re: Should URL's be pervasive. Message-ID: <20010903021946.A377@dylan.home> Mail-Followup-To: Steve Roome , David O'Brien , Keith Stevenson , Leo Bicknell , freebsd-hackers@freebsd.org References: <20010830111018.A97057@ussenterprise.ufp.org> <20010830111708.A20961@osaka.louisville.edu> <20010830232109.A1077@dylan.home> <20010831153409.A27173@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831153409.A27173@dragon.nuxi.com>; from dev-null@NUXI.com on Fri, Aug 31, 2001 at 03:34:09PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 03:34:09PM -0700, David O'Brien wrote: > On Thu, Aug 30, 2001 at 11:21:09PM +0100, Steve Roome wrote: > > ping http://www.myserver.wherever/ > > instead of telnet wherever 80, just to see if I get a connected or > > not ? > > Do you have *ANY* clue how ping works? Ping uses ICMP packets; not TCP, > not UDP -- thus there is NO concept of ports. And what does "instead of > telnet mean"?? Again, do you have any clue how ping works? I certainly understand that ping currently works on ICMP, and that a feature enhancement to allow it to use a different type of packet might be, perhaps to some, a useful addition to its capability. Considering, for example, that an ICMP packet may take a very different route to (and hence time to reach) the destination machine comparted to a TCP/IP packet containing http information it might not be such a bad idea. e.g. Transparent web proxies. Had you read the thread of course, you may have noticed that I was merely replying to someone else who has asked about this sort of functionality. But feel free to take a dig at _me_ anyway, I won't be frightened away from it all just yet. Luckily I'm not a new user who's going to take harshly and hate us bloody arrogant unix zealots though. > To the person that wants to "traceroute http://www.myserver.wherever/", > do you have *ANY* clue how traceroute works? You cannnot use a port that > something is answering on. Again, if you've got a transparent web proxy in the way, this would be a really nice feature. I've not got a clue how to implement it though, it would probably involve changing the way rather a lot of network hardware works, I just commented on it. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message