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

[Bug 213] Spec inconsistent on PROPFIND/Depth:infinity

From: <bugzilla@soe.ucsc.edu>
Date: Fri, 10 Feb 2006 16:49:35 -0800
Message-Id: <200602110049.k1B0nZD2009215@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

lisa@osafoundation.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From lisa@osafoundation.org  2006-02-10 16:49 -------
Trying to think about the consequences and backward-compatibility here, I think
this should read:

   "A client MUST submit a Depth header with a value of "0", "1", or "infinity"
with a PROPFIND request.  Servers MUST support "0" and "1" depth requests on
WebDAV-compliant resources and SHOULD support "infinity" requests. In practice,
support for depth infinity requests MAY be disabled, due to the performance and
security concerns associated with this behavior. Since clients weren't required
to include the Depth header in [RFC2518], servers SHOULD treat such a request as
if a "Depth: infinity" header was included. "

I'm not sure if we concluded that the servers SHOULD or MAY support infinity
PROPFIND.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
You are on the CC list for the bug, or are watching someone who is.
Received on Saturday, 11 February 2006 00:49:40 GMT

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