[caldeveloper-l] CALDAV:calendar-data & CARDDAV:address-data

[Helge Hess]

On 6. Jan 2018, at 15:57, Ken Murchison <murch at fastmailteam.com> wrote:
> Hi Helge,
> 
> 207 response with 403 in propstat, correct?

Yes.

> Along the same lines, what if one of these properties is included in a REPORT request with an invalid/unsupported content-type or version, e.g.:
> 
> <CALDAV:calendar-data content-type="foo/bar" />
> 
> My server currently fails outright with 403 and a precondition of CALDAV:supported-calendar-data

Puh, good question as well.

Well, I would think that this should be in a 403 propstat too. In the real world I guess it doesn’t really matter and what you do might actually be the ‘safer’ choice.

hh

P.S. :I really dislike those parts of CalDAV - content should not be fetched as part of such a query but w/ GETs (inside a ßATCH :->), this would give you all the content negotiation already built into CalDAV. And w/ HTTP/2 it could be even pushed.


> On 01/06/2018 09:52 AM, Helge Hess wrote:
>> That is a really good question.
>> 
>> I think I would go w/ 403. 404 suggests that the client could create it (which a CalDAV server should block to not overload the name).
>> 
>> hh
>> 
>>> On 6. Jan 2018, at 15:47, Ken Murchison <murch at fastmailteam.com> wrote:
>>> 
>>> All,
>>> 
>>> While reviewing the specs and my code, I stumbled upon this in RFC 4791 (and similar text in RFC 6352):
>>> 
>>>    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.
>>> 
>>> 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 ... ?
>>> -- 
>>> Kenneth Murchison
>>> Cyrus Development Team
>>> FastMail Pty Ltd
>>> 
>>> _______________________________________________
>>> caldeveloper-l mailing list
>>> caldeveloper-l at lists.calconnect.org
>>> http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org
>> _______________________________________________
>> caldeveloper-l mailing list
>> caldeveloper-l at lists.calconnect.org
>> http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org
> 
> -- 
> Kenneth Murchison
> Cyrus Development Team
> FastMail Pty Ltd
> 
> 
> -- 
> Kenneth Murchison
> Cyrus Development Team
> FastMail Pty Ltd
> _______________________________________________
> caldeveloper-l mailing list
> caldeveloper-l at lists.calconnect.org
> http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org