- From: <bugzilla@soe.ucsc.edu>
- Date: Sun, 20 Nov 2005 12:13:08 -0800
- To: w3c-dist-auth@w3.org
http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=177
Summary: "PROPFIND status codes" section
Product: WebDAV-RFC2518-bis
Version: -08
Platform: Other
URL: http://http://greenbytes.de/tech/webdav/draft-ietf-
webdav-rfc2518bis-08.html#rfc.section.8.2.1
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: 08. HTTP Methods for Distributed Authoring
AssignedTo: joe-bugzilla@cursive.net
ReportedBy: julian.reschke@greenbytes.de
QAContact: w3c-dist-auth@w3.org
"A server MAY fail an entire PROPFIND request with an appropriate status code
and MAY redirect the entire request."
This is true for any HTTP request. Saying it here explicitly may cause people to
wonder whether this is true for other methods defined here...
"In addition, the following error codes are specifically defined for PROPFIND
requests:
403 Forbidden - A server MAY reject all PROPFIND requests on collections with
depth header of "Infinity", in which case it SHOULD use this error with the
element 'propfind-infinite-depth-forbidden' inside the error body."
1) No, 403 is not defined specifically for PROPFIND.
2) A server MAY reject them also if the resource is not a collection (why check
first???)
3) I think the part about the response body is only understandable to people who
already knew that. Let's have one piece in the earlier sections that defines
the error response body in a consistent way with RFC3253, then just define a
precondition name here.
The text goes on listing 4 specific status codes to which I object:
1) As far as I can tell, nobody asked for that restriction, and worse:
2) There's an IESG-accepted spec that already shows another status code that can
be used here
(<http://greenbytes.de/tech/webdav/draft-reschke-webdav-property-datatypes-latest.html#rfc.section.4.2>),
which IMHO is a real-world proof that this subsection is not only unnecessary,
but also harmful.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Sunday, 20 November 2005 20:13:14 UTC