[Syncevolution-issues] [Bug 77424] New: VJOURNAL: handle UID uniqueness error message

https://bugs.freedesktop.org/show_bug.cgi?id=77424 Priority: low Bug ID: 77424 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Summary: VJOURNAL: handle UID uniqueness error message Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: 1.4 Component: CalDAV/CardDAV Product: SyncEvolution Apple Calendar server refuses to create a new VJOURNAL item if the UID is not unique. This started happening in nightly testing when introducing POST support. Before that, SyncEvolution would automatically use the same URL for old and new item and therefore detect the conflict and return "was merged" - see: http://downloads.syncevolution.org/syncevolution/archive/test-results/syn... When PUT fails, we get a "code 412, class 4, Precondition Failed" error which triggers a search for the UID. When POST fails, we get a very less specific "code 403, class 4, Forbidden" error back with more details in the XML body: [DEVELOPER 00:00:14] stderr: Read block (364 bytes): [DEVELOPER 00:00:14] stderr: [<?xml version='1.0' encoding='UTF-8'?> [DEVELOPER 00:00:14] stderr: <error xmlns='DAV:'> [DEVELOPER 00:00:14] stderr: <no-uid-conflict xmlns='urn:ietf:params:xml:ns:caldav'> [DEVELOPER 00:00:14] stderr: <href xmlns='DAV:'>/calendars/__uids__/user01/tasks/c5490e736b6836c4d353d98bc78b3a3d.ics</href> [DEVELOPER 00:00:14] stderr: </no-uid-conflict> [DEVELOPER 00:00:14] stderr: <error-description xmlns='http://twistedmatrix.com/xml_namespace/dav/'>UID already exists</error-description> [DEVELOPER 00:00:14] stderr: </error>] [DEVELOPER 00:00:14] stderr: Running post_send hooks [DEVELOPER 00:00:14] stderr: ah_post_send (#0), code is 403 (want 401), WWW-Authenticate is (none) [DEVELOPER 00:00:14] stderr: Request ends, status 403 class 4xx, error line: [DEVELOPER 00:00:14] stderr: 403 Forbidden [DEBUG 00:00:14] POST: bad HTTP status: <status 1.1, code 403, class 4, Forbidden>, must not retry The current handling of that is to do the same UID search, just in case that a UID conflict might be the reason. It would be better to parse the XML body and save the roundtrip time for the search. Probably not that important, though. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.