User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce: 1. Add a network Caldav calendar (actually tested with Radicale server). 2. Add this same calendar to an other Caldav client (actually tested with Caldavzap). 3. Add an event with the other client. 4. Add an event with lightning Actual results: At step 4, lightning send a PUT request with entire calendar (like PUT /my/calendar.ics/) whereas other client (like tested on Caldavzap) send a PUT request with only new event (like PUT /my/calendar.ics/eventid.ics). Result is: lightning override previously created event with an other client. Expected results: a. lightning should send a PUT request with only the event b. lightning can systematically retrieve calendar to merge it with new event before send it Question: There is a reason for make this entire calendar PUT instead PUT the event ?
Related to: https://github.com/Kozea/Radicale/issues/548 . PRoblem fixed with application of solution explained in radicale github issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.