When are and aren't two URLs the same? (ports)
joaquin at netmesh.us
Sat Apr 15 00:17:45 UTC 2006
This argument applies to the special cases mentioned, Port 80 and the
We also need to consider the general case.
> > Do these URLs:
> > http://example.com/joe
> > http://example.com:80/joe
> > represent the same identity?
>I say yes. Not only from a practical standpoint, but also a technical
>one. My interpretation of the HTTP spec is that this is a perfectly
>valid translation to make, based on the following:
> >From 3.2.2, regarding URLs: If the port is empty or not given, port 80
> >From 14.23, regarding the Host header: A "host" without any trailing
>port information implies the default port for the service requested
>(e.g., "80" for an HTTP URL)
>To me, this is no different than assuming that the identity
>"http://joe.example.com" and "http://joe.example.com/" are identical.
>The trailing slash, identifying the root path as part of the identity,
>is optional and assumed.
>(Helps to actually send this to the list address :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the yadis