Proposal (Was: When are and aren't two URLs the same?)

Joaquin Miller joaquin at
Mon Apr 24 17:50:43 UTC 2006

>>How about the case when there are . or .. components in the 
>>absolute path part of an URL?
>>Including when those which are trailing without a slash.
>>E.g. Should and 
>> be the same?
>>What about vs
>Nothing should be done in that case.  Those pairs of URLs aren't the 
>same, even if some servers will provide the same content for 
>them.  Just because the path section of a URL looks like a Unix path 
>doesn't mean that it is or should be treated as a Unix path.

I very much agree with this.

We need a solid answer to the problem posed (for which real examples 
have already surfaced).  The two main candidates are the rewriting 
rules we are working on and the strict rule.  Rewriting may actually 
be more robust in practice, since URL changes may be going on in 
libraries, without implementers being aware of the changes.

But, if we decide to rewrite, we should be strict about that, 
too.  The rules for treating different URLs as equivalent should be 
based only on what comes from the standards. (Example: 80 is the 
default HTTP port, so is equivalent to but   is NOT 
equivalent to  (You notice that Eudora has 
again decided that the period is not part of the URL.  That's a case 
that we need to keep in mind.))

Cordially, Joaquin

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the yadis mailing list