Re: [Evolution] Problem in write support CalDAV 3.16

[Adam Tauno Williams <awilliam whitemice org>]

On Wed, 2015-05-13 at 07:51 +0200, Milan Crha wrote:
> On Tue, 2015-05-12 at 10:31 +0200, Matthijs van Wolferen LL.M wrote:
> >         < Allow: OPTIONS, GET, HEAD, POST, DELETE
> >         < Allow: PROPFIND, REPORT, PROPPATCH, MKCOL, ACL
> >         < Allow: MKCALENDAR
> the CalDAV code checks whether the 'Allow' response header contains
> 'PUT' and 'DELETE'. If it does, it marks the calendar as writable. 
> You
> calendar, interestingly, misses the 'PUT'.

You beat me to it.  Without PUT WebDAV [which CalDAV is] is read-only.

> Thus that might be the reason why the calendar is marked as read
> -only.

If the above is accurate it SHOULD be displayed as read-only.  This is
a server/provider bug and a client behaving correctly.


-- 
Adam Tauno Williams <mailto:awilliam whitemice org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA