Oh god, as everybody else is saying, I can't believe I'm getting involved
in this, but...
On Fri, Aug 31, 2001 at 09:58:21AM -0700, a little birdie told me
that Richard Hodges remarked
>
> Why not parse it literally? For instance, http://www.ufp.org
> would imply TCP, dest port 80, and host www.ufp.org.
>
> For ping, that would imply that I want to test the three-way
> handshake on whatever is listening on port 80 at www.ufp.org
>
> For traceroute, I want to send a series of TCP SYN packets to
> www.ufp.org, port 80 with increasing TTL values. Perhaps this
No, it doesn't.
http://www.ufp.org/ does NOT mean TCP port 80.
www.ufp.org:80 means port 80, I don't know of any simple common way to
say TCP.
http://www.ufp.org/ means the host 'www.ufp.org' using the protocol
'http' with the TCP port 80 implicity as a result of the 'http'.
Traceroute is not going to use HTTP. Ping is not going to use HTTP.
Rpcinfo is not going to use HTTP. A mail client is not going to use
HTTP (this one is perhaps debatable, but I'm sure as hell not going
there).
If you want to take a URI passed to 'ping', say, and parse out a
hostname, that's one thing which I'm sure we could have endless
disagreement about. But doing that is *NOT* parsing it as a URI.
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Unix Systems Administrator | [EMAIL PROTECTED]
Specializing in FreeBSD | http://www.over-yonder.net/
"The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
