<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>All,</p>
<p>While reviewing the specs and my code, I stumbled upon this in
RFC 4791 (and similar text in RFC 6352):</p>
<pre class="newpage"> Note: The CALDAV:calendar-data XML element is specified in requests
and responses inside the DAV:prop XML element as if it were a
WebDAV property. However, the CALDAV:calendar-data XML element is
not a WebDAV property and, as such, is not returned in PROPFIND
responses, nor used in PROPPATCH requests.
</pre>
<p>Given this, what is the proper server response if these
"properties" are included in a PROPFIND request? Should the
PROPFIND fail outright with a 403 (Forbidden) or should the
property be listed for each resource with a propstat of 403
(Forbidden), or 404 (Not Found), or ... ?<br>
</p>
<pre class="moz-signature" cols="72">
--
Kenneth Murchison
Cyrus Development Team
FastMail Pty Ltd</pre>
</body>
</html>