• To: xml-dev@l...
• Subject: Re: URL resolution sanity check
• From: richard@i... (Richard Tobin)
• Date: Mon, 18 Jul 2005 18:33:57 +0100 (BST)
• Cc:
• In-reply-to: <42D0F2EA.4090007@m...>
• Organization: HCRC, University of Edinburgh

In article <42D0F2EA.4090007@m...> 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

• References:
  • Re: URL resolution sanity check
    • From: Elliotte Harold <elharo@m...>

• Prev by Date: Re: Mixed content in data-binding (Was: Re: Interesting pair of comments
• Next by Date: Dont Miss Extreme Markup Languages 2005 -- Two Weeks Away
• Previous by thread: Re: URL resolution sanity check
• Next by thread: Re: URL resolution sanity check
• Index(es):
  • Date
  • Thread