[CalDAV] Decide better response on PUT of components with attendees
Creating e new Task with attendees, Evolution-Data-Server calls over CalDAV:
> PUT /dav/calendars/user/zzz/Default/f20b91470dd9de78ac8d4186e82cad4c38dbce4d.ics HTTP/1.1
> Prefer: return=minimal
> BEGIN:VCALENDAR
> CALSCALE:GREGORIAN
> PRODID:-//Ximian//NONSGML Evolution Calendar//EN
> VERSION:2.0
> BEGIN:VTODO
> ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
> RSVP=TRUE:mailto:her@example.com
> END:VTODO
> END:VCALENDAR
and expects an Etag. The server does attach a SCHEDULE-STATUS attribute to the ATTENDEE and therefore does not return an ETag on PUT. Evolution-data-server calls a GET afterwards to obtain the ETag. The behaviour of the server is foreseenable, if it follows all the specification.
- When creating a VEVENT or VTASK, upload the data with
Prefer: return=representation
, so that the server can return the ETag and no subsequent GET will be called.
Edited by Milan Crha