<html>
<body>
<font size=3>This argument applies to the special cases mentioned, Port
80 and the trailing slash.<br><br>
We also need to consider the general case.<br><br>
<blockquote type=cite class=cite cite="">> Do these URLs:<br>
>
<a href="http://example.com/joe" eudora="autourl">
http://example.com/joe</a><br>
>
<a href="http://example.com/joe" eudora="autourl">
http://example.com:80/joe</a><br>
> represent the same identity?<br><br>
I say yes. Not only from a practical standpoint, but also a
technical<br>
one. My interpretation of the HTTP spec is that this is a perfectly<br>
valid translation to make, based on the following:<br><br>
>From 3.2.2, regarding URLs: If the port is empty or not given, port
80<br>
is assumed.<br><br>
>From 14.23, regarding the Host header: A "host" without any
trailing<br>
port information implies the default port for the service requested<br>
(e.g., "80" for an HTTP URL)<br><br>
<a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html" eudora="autourl">
http://www.w3.org/Protocols/rfc2616/rfc2616.html</a><br><br>
To me, this is no different than assuming that the identity<br>
"<a href="http://joe.example.com/" eudora="autourl">
http://joe.example.com</a>" and
"<a href="http://joe.example.com/" eudora="autourl">
http://joe.example.com/</a>" are identical.<br>
The trailing slash, identifying the root path as part of the
identity,<br>
is optional and assumed.<br><br>
(Helps to actually send this to the list address :)<br><br>
- K.Howe</font></blockquote></body>
</html>