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

[Bug 147] CLARIFY_UNTAGGED_IF_HEADER_APPLICATION

From: <bugzilla@soe.ucsc.edu>
Date: Mon, 16 Jan 2006 20:05:34 -0800
Message-Id: <200601170405.k0H45YV8005141@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

lisa@osafoundation.org changed:

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



------- Additional Comments From lisa@osafoundation.org  2006-01-16 20:05 -------
I propose slightly different wording because when we reverse the requirement, I
think it doesn't matter whether depth is defined for that method.  Removing that
makes the wording clearer.  We can also state the principle that depth does not
combine with other headers as a default, to explain the related requirement.

   By default, the Depth header does not interact with other headers. 
   That is, each header on a request MUST be applied only to the 
   Request-URI if it applies to any resource, unless specific Depth behavior
   is defined for that header. 





------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Tuesday, 17 January 2006 04:05:38 GMT

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