W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005


From: <bugzilla@soe.ucsc.edu>
Date: Thu, 13 Oct 2005 08:34:22 -0700
Message-Id: <200510131534.j9DFYMRo008227@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org


           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

Raised by Kevin Wiggen:
(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

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:33 UTC