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

Re: GULP 5.6 vs issue UNLOCK_WHAT_URL (65)

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Sat, 12 Jun 2004 13:34:25 -0400
To: Julian Reschke <julian.reschke@gmx.de>
Cc: w3c-dist-auth@w3.org, w3c-dist-auth-request@w3.org
Message-ID: <OF7C34425B.E8C9F51A-ON85256EB1.00608127-85256EB1.00609227@us.ibm.com>
I agree.

Cheers,
Geoff

Julian wrote on 06/12/2004 09:45:50 AM:

> Julian Reschke wrote:
> 
> here are some actual test results:
> 
> a) Apache/moddav: allows UNLOCK on indirectly locked resources,
> b) Xythos: same,
> c) SAP Enterprise Portal: same,
> d) Microsoft IIS: no support for depth infinity locks.
> 
> Thus the current text in the issues resolution "Resolved that you can 
> specify any URL locked by the lock you want to unlock" does indeed 
> reflect current implementation experience, and this is what spec 
> revisions should be saying.
> 
> Thus:
> 
> 1) RFC2518bis should undo that change, and
> 2) GULP should be updated accordingly (I'll do that for my in-document 
> copy of GULP at 
> <http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking-
> latest.html#rfc.section.C>.
Received on Saturday, 12 June 2004 13:37:16 GMT

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