On Fri, 31 Aug 2001, Paul Richards wrote:
> A URI is a Universial Resource Indicator, it's not a web browser address.
>
> On the other hand, what exactly is http://www.ufp.org supposed to be useful
> for when www.ufp.org is the same thing.
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
would be a way to test connectivity to a service behind a firewall.
Perhaps this would be just another DOS tool for lamers...
For email, this would not make a lot of sense. Should my mailer
try to connect to port 80 and start with "ehlo www.ufp.org"?
After all, I *DID* use the http:// prefix...
Using "ftp mailto:[EMAIL PROTECTED]"; could imply that I want to
send a file to someone via email.
On second thought, it looks like most Internet apps would have to
be rewritten to understand this new functionality.
> What would happen if I did mutt http://www.ufp.org ?
In this case, mutt should do an HTTP request to port 80 at www.ufp.org,
grab the home page, and put it in your inbox :-)
<smirk>
-Richard
-------------------------------------------
Richard Hodges | Matriplex, inc.
Product Manager | 769 Basque Way
[EMAIL PROTECTED] | Carson City, NV 89706
775-886-6477 | www.matriplex.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
