Re: Recognizing a WebDAV enabled client

Hi Michael,

> right, this might makes sense for formats. But I would argue with 
> another usecase, namely Custom Authentication
> instead of HTTP authentication (BASIC or DIGEST).
>
> Let's assume a resource is protected and a server would like to offer 
> custom authentication, e.g. it would send
> a HTML to a regular browser and some WebDAV specific XML to a WebDAV 
> enabled client, whereas I haven't digged into
> WebDAV far enough how something like this could be handled by the 
> WebDAV spec.
as Julian pointed out, this form of authentication is not covered by any 
specification, so there is no reliable way for a generic client to 
handle it anyway (besides the fact that authentication has nothing to do 
with WebDAV).

Regards,
Manfred