Re: [xml-dev] URL resolution sanity check

In article <> you write:

>The problem is that both 2396 and 3986 remove the segment following the 
>last slash *before* removing dot segments. Thus 
>http://www.example.com/data/limit/.. and 
>http://www.example.com/data/limit/../ do not get treated the same.

This may be a bug - ask the TAG to look at it.  Note that it doesn't
happen unless the user specifies it literally in a base URI, because a
trailing /.. is removed at the end of the algorithm, so URIs ending
with .. are never generated.

This is not just an XML question - HTML's <base> element must have
the same problem.  So presumably there are plenty of implementations
to test.

-- Richard