W3C home > Mailing lists > Public > uri@w3.org > January 2006

Re: http-urls style, trailing slash and webdav

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 26 Jan 2006 17:35:07 +0100
Message-ID: <43D8FA3B.3080403@gmx.de>
To: Reto Bachmann-Gmür <reto@gmuer.ch>
CC: uri@w3.org

Reto Bachmann-Gmür wrote:
> Julian Reschke schrieb:
>> Reto Bachmann-Gmür wrote:
>>> ...
>>> However implementing support for webdav all the clients I tested at 
>>> least occasionally requested a collection without trailing slash, 
>>> even if was referenced with slash in the containing collection, this 
>>> makes it impossible to have two differen resource at 
>>> http://wymiwyg.org/knobot (a GET-dereferencable resource) and 
>>> http://wymiwyg.org/knobot/ (a dav:collection). It seems that the 
>>> expected behavior is  that an URL with removed trailing slash either 
>>> causes the same server response or a redirect to the resource with 
>>> trailing slash.
>> Yes. So why don't you just make it one resource that is both a 
>> DAV:collection and has GETtable content?
> The problems I see are:
> - Relative URIs in formats such as HTML or N3

Wouldn't that be solved with Content-Location (not sure...).

> - Search engines index twice (maybe not with proper Content-Location 
> header)
> - Ambiguity when comparing meta-information (such as bookmark files, or 
> annotea annotations)
> Maybe a work around:
> - On GET/POST/PUT requests with a slash at the end: redirect to the url 
> without slash, except for "/"
> - On PROPFIND/PROPATCH requests without slash at the end: deliver 
> response for the resource with trailing slash iff this is a DAV:collection

Why wouldn't you always want to point the client to the variant with 
trailing slash?

> ...

Best regards, Julian
Received on Thursday, 26 January 2006 16:37:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:09 UTC