Re: URI Templates - optional variables?

On Aug 1, 2007, at 3:26 AM, Stefan Eissing wrote:
>
> Am 31.07.2007 um 21:30 schrieb Mike Schinkel:
>> Stefan Eissing wrote:
>>> converter MUST perform path resolution as described in RFC
>>> 3986 ch. 5.2.3 and 5.2.4. That will also stop some injections
>>> of "." and ".." into URIs while saving the client from
>>> worrying to much about double "/" and such.
>>
>> I read the spec but am one that still has trouble understanding  
>> portions of
>> a spec that do not include examples such as those. Which of the  
>> following
>> are you saying it should result in?
>>
>> A.) http://www.example.com/
>> B.) http://www.example.com//
>
> Clearly A. The path resolution will always make conversions such as:
>
> //  ->  /
> /./  ->  /
> /a/../b -> /b
>
Looking at the referenced sections its not clear to me that // gets  
converted to /. Can you point me to the step in the algorithm that  
would accomplish that ?

Thanks,
Marc.

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

Received on Wednesday, 1 August 2007 14:48:07 UTC