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

RE: need clarification about COPY to locked resource response cod e

From: <gclemm@rational.com>
Date: Fri, 25 Jan 2002 08:18:05 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B105A31608@SUS-MA1IT01>
To: w3c-dist-auth@w3.org
I believe a client should accept either behavior.  Section 8.8.5 explicitly
states that a 423 indicates that the destination resource was locked,
so there is no ambiguity about whether the 423 refers to the source
or the destination.

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Friday, January 25, 2002 7:37 AM
To: WebDAV
Subject: need clarification about COPY to locked resource response code


Hi,

when running the Litmus test suite against our server, we came across the
following problem for lock test 8 (COPY):

In this test case, a non-locked resource is copied to a locked resource
without giving the lock token in the If: header.

Litmus expects the server to return 423 LOCKED (and this is what moddav
does).

Both our server and IIS however return a 207 MULTISTATUS, and have a
response element for the *destination URI* with an 423 LOCKED status.

I think the latter is correct, because the problem isn't with the request
URI.

In the section about COPY behaviour for *collections*, RFC2518 says [1]:

"If an error in executing the COPY method occurs with a resource other than
the resource identified in the Request-URI then the response MUST be a 207
(Multi-Status)."

I think this should apply to copying non-collections as well.

Julian




[1] <http://www.greenbytes.de/tech/webdav/rfc2518.html#rfc.section.8.8.3>
Received on Friday, 25 January 2002 08:19:11 GMT

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