Calendar sync breaks when a repeating event is being removed/edited from the phone



  • Well I have access to the server too and I was checking the log files from other calDav apps on phones and PCs but this happens only with davdroid.I’ve been using other calDav apps like Thunderbird Lightning, calDav, and some built in calDav apps on Blackberry phones and they dont show this behavior. All apps can edit/delete repeating events without an issue, so I assumed that this could be an issue with the way davdroid tries to sync the event. Since I had no time to read the dav rfc and get extensive knowledge of what are the different ways to sync such repeating events and if there is difference at all.
    It could be an issue with the Zimbra server too but I would need some more time to read the rfc and compare the different commands send from different apps for such repeating events.

    I thought this could be an issue with an encoding or an escaping of a char:

    V/davdroid.URIUtils( 3818): Normalized URL https://myhost.com/dav/beji@myhost.com/Life/20150106T162843Z-3818@4a7fb4f123ef0858.ics -> https://myhost.com/dav/beji@myhost.com/Life/20150106T162843Z-3818@4a7fb4f123ef0858.ics
    V/davdroid.URIUtils( 3818): Normalized URL https://myhost.com/dav/beji@myhost.com/Life/20150106T162843Z-3818@4a7fb4f123ef0858.ics -> https://myhost.com/dav/beji@myhost.com/Life/20150106T162843Z-3818@4a7fb4f123ef0858.ics
    I/davdroid.DavRedirectStrategy( 3818): Following redirection: PUT /dav/beji@myhost.com/Life/20150106T162843Z-3818_4a7fb4f123ef0858.ics -> https://myhost.com/dav/beji@myhost.com/Life/20150106T162843Z-3818@4a7fb4f123ef0858.ics
    E/davdroid.DavSyncAdapter( 3818): Hard HTTP error 403
    

    I/davdroid.DavRedirectStrategy( 3818): Following redirection: PUT /dav/beji@myhost.com/Life/20150106T162843Z-3818_4a7fb4f123ef0858.ics -> https://myhost.com/dav/beji@myhost.com/Life/20150106T162843Z-3818@4a7fb4f123ef0858.ics

    The _ is translated as @ but this is based on my programming knowledge which are poor 🙂

    If I can help with server log files or any additional investigation steps do let me know?


  • developer

    Initially, DAVdroid choses 20150107T091217Z-11621_4a7fb4f123ef0858.ics as a file name (it’s the UID, with “@” replaced by “_” because I don’t like “@” in file names) and tries to PUT the file there:

    D/Wire (11621): http-outgoing-3 >> “PUT /dav/beji@myhost.com/Calendar/20150107T091217Z-11621_4a7fb4f123ef0858.ics HTTP/1.1[\r][\n]”

    Zimbra tells DAVdroid to put it there instead, i.e. use the exact UID as file name:

    D/Wire (11621): http-outgoing-3 << “Location: https://myhost.com/dav/beji@myhost.com/Calendar/20150107T091217Z-11621@4a7fb4f123ef0858.ics[\r][\n]

    This is a legitimate request, no problem. So DAVdroid tries again at the requested URL:

    D/Wire (11621): http-outgoing-3 >> “PUT /dav/beji@myhost.com/Calendar/20150107T091217Z-11621@4a7fb4f123ef0858.ics HTTP/1.1[\r][\n]”

    … and your server says Forbidden:

    D/Wire (11621): http-outgoing-3 << “HTTP/1.1 403 Forbidden[\r][\n]”

    I don’t see any problems on DAVdroid side here. Did you already create an issue for Zimbra?



  • I see, not yet but I am going to do it now. Also I would try to workaround it ,too bad it is the company server i can not restart and tweak whenever I like but will find a donwtime window to play a bit with it. If I find a workaround will post here since it might be useful to somebody else. Thanks for the prompt and detailed answer.


  • developer

    Ok, if there’s anything new, please just post here.



  • Update:
    The issue is still observed even with the newest version of Zimbra( 8.6.0_GA_1153.FOSS ). Various configurations are yet to be tweaked.


  • developer

    Did you already manage to open an issue for Zimbra? I think there won’t be changes unless the developers are notified of this issue. It shouldn’t take too much time, basically just send a link to this discussion.


  • developer

    Any news about this?



  • hi rfc2822,

    The issue opened at Zimbra community is here:
    http://community.zimbra.com/collaboration/f/1897/t/1138400

    sorry for not providing an update for almost 20 days, I have been checking different config options and issues that could have been caused by the migration script from an earlier version of Zimbra here https://community.zimbra.com/collaboration/f/1894/p/1122336/1543492

    Debugging on a live mail server usually is slow due to the many downtime windows that must be planed in order not to disturb the users.

    I am going to keep updating this issue once I have any more information/solution/workaround.

    cheers,
    beji



  • This case is officially acknowledged as a bug at Zimbra Server and could be followed at https://bugzilla.zimbra.com/show_bug.cgi?id=98199.

    cheers,
    beji


  • developer

    This is another result of #170, please follow up there.


Log in to reply
 

Similar topics