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

[Bug 95] possible LOCK response codes

From: <bugzilla@soe.ucsc.edu>
Date: Tue, 6 Dec 2005 11:52:43 -0800
Message-Id: <200512061952.jB6JqhDB000815@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=95





------- Additional Comments From julian.reschke@greenbytes.de  2005-12-06 11:52 -------
I have checked with Xythos, Apache and Netweaver (IIS does not support deep locks).

Xythos and Apache indeed return a 424 for the resource at the Request-URI, while
Netweaver returns a 403. All of them report 423 for the child resource that
caused the lock not to be granted.

I don't see an interop problem here, but if there's consensus that the resource
at the request URI really needs to be reported at all, and that it must be
reported with 424, we'll happily change our impl.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Tuesday, 6 December 2005 19:52:52 GMT

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