Re: [Evolution] Problem in write support CalDAV 3.16

[Milan Crha <mcrha redhat com>]

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

        Hi,
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'.

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

Please note that there had been some issues with proper propagation of
the writeability from the backend to the client in pre-3.16.0 versions
too.
        Bye,
        Milan