W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2001

Retrieving the lockdiscovery property from a non locked resource

From: Hartmut Warncke <hwarncke@Adobe.COM>
Date: Thu, 15 Mar 2001 11:12:57 +0100
Message-ID: <3AB095A9.80024A0C@adobe.com>
To: WebDAV WG <w3c-dist-auth@w3.org>

Hi all,

if '/a.html' is a resource which is  *not*  locked and the client sends
a ...

<D:propfind xmlns:D="DAV:">
     <D:prop>
         <D:lockdiscovery/>
     </D:prop>
</D:propfind>

... on that resource, the mod_dav server responds witth a:

 <?xml version="1.0" ...>
    <D:multistatus xmlns:D="DAV:">
        <D:response>
            <D:href>
                /a.html
            </D:href>
            <D:propstat>
                <D:prop>
                    <D:lockdiscovery/>
                </D:prop>
                <D:status>
                    HTTP/1.1 200 OK
                 </D:status>
                ...
So, mod_dav sends an empty lockdiscovery element.

IIS responds with:
...
<a:response>
    <a:href>
        /a.html
    </a:href>
    <a:propstat>
        <a:status>
            HTTP/1.1 200 OK
        </a:status>
        <a:prop/>
    </a:propstat>
</a:response>
...

So, IIS sends no lockdiscovery property at all.

In RFC2518; section 8.1 I found the following sentence:

"A request to retrieve the value of a property which does not exist is
an error and MUST be noted, if the response uses a multistatus XML
element, with a response XML element which contains a 404 (Not Found)
status value."

Does this sentence applies only to user-defined properties and not to
DAV build-in properties like the lockdiscovery property?

What is the correct server behaviour?

Best, Hartmut
Received on Thursday, 15 March 2001 05:13:32 GMT

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