- From: <bugzilla@soe.ucsc.edu>
- Date: Thu, 13 Oct 2005 08:34:22 -0700
- To: w3c-dist-auth@w3.org
http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=124
Summary: REPORT_OTHER_RESOURCE_LOCKED
Product: WebDAV-RFC2518-bis
Version: -07
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: 10. Status Code Extensions to HTTP/1.1
AssignedTo: joe-bugzilla@cursive.net
ReportedBy: elias@cse.ucsc.edu
QAContact: w3c-dist-auth@w3.org
In some cases, such as when the parent collection of a resource is locked, a 423
(Locked) status code is returned even though the resource identified by the
Request-URI is not locked. This can be confusing, since it is not possible for a
client to easily discover which resource is causing the locked status code to be
returned. An improved status report would indicate the resource causing the lock
message.
Raised by Kevin Wiggen:
http://lists.w3.org/Archives/Public/w3c-dist-auth/1999JulSep/0039.html
(Point #1)
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Thursday, 13 October 2005 15:34:32 UTC