W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2006

Re: Recognizing a WebDAV enabled client

From: Michael Wechner <michael.wechner@wyona.com>
Date: Fri, 30 Jun 2006 10:20:37 +0200
Message-ID: <44A4DED5.1060705@wyona.com>
To: Julian Reschke <julian.reschke@gmx.de>
CC: Jan Algermissen <jalgermissen@topicmapping.com>, w3c-dist-auth@w3.org

Julian Reschke wrote:
> Jan Algermissen schrieb:
>> Hi,
>>
>> On Jun 30, 2006, at 9:50 AM, Julian Reschke wrote:
>>
>>> Michael Wechner schrieb:
>>>> Hi
>>>> It's not clear to me how a server can recognize a WebDAV enabled 
>>>> client from a GET request and
>>>
>>> It can't.
>>
>> I will run into the same question in the near future, so let me get 
>> this right:
>>
>> I have implemented an HTTP resource for something collection-like and 
>> like to serve that up as HTML lists or WebDAV collections depending 
>> on the client capabilities. Are you saying I cannot detect if I am 
>> talking to a client that can handles WebDAV collections or not? 
>> That's seems silly.
>
> If a client does a GET on that URL, return HTML. If a client does a 
> PROPFIND on that URL, return a XML multistatus response body.

this might working for collections, because PROPFIND exists ;-) and 
hence allows differentiation
>
> What am I missing?

as I described I think there are good reaons that also a GET request 
needs differentiation, but also more generally being
able to recognize the version.

Thanks

Michi
>
> Best regards, Julian
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61
Received on Friday, 30 June 2006 08:20:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:14 GMT