W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2004

Re: LOCK refresh on indirectly locked resource

From: Joe Orton <joe@manyfish.co.uk>
Date: Mon, 13 Sep 2004 09:57:29 +0100
To: "'Webdav WG'" <w3c-dist-auth@w3c.org>
Message-ID: <20040913085729.GA28982@manyfish.co.uk>

On Sun, Sep 12, 2004 at 07:39:43PM +0200, Julian Reschke wrote:
> It's some time ago that somebody asked how servers implement this today. 
> I finally got around to write a test case (attached JScript), including
> 
> 1) using a no-tag list If header,
> 2) using a tagged If header, specifying the lock root and
> 2) using a tagged If header, specifying the indirectly locked resource.

Is your latter (2) behaviour defined by 2518 or 2518bis? I suppose both
are equivalent by 2518 at least.

> Results:
...
> Apache2.0.50/mod_dav: *crashes*, see 
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31183>

It looks like the code path for indirectly refreshing the lock had never
been tested in mod_dav, it has never worked AFAICT. I can't find any
reports of this bug being triggered before, either, so I guess this is
not the most widely used protocol feature...

(I've made a new release of the litmus test suite which also includes a
test for an indirect lock refresh for any others who are interested and
can't run JScript: http://www.webdav.org/neon/litmus/)

Regards,

joe
Received on Monday, 13 September 2004 08:58:03 GMT

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