Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
0013806: CalDAV Server responds with 404 #6828
Reported by shochdoerfer on 22 Mar 2018 16:09
Version: 2018.02.1 Community Edition
Sometimes the CalDAV Server responds with 404 reponse which some clients happily ignore, iCal on iOS presents this error to the user by showing an alert box. This is what I have found out so far:
This is the request that returns a 404 in our Tine 2.0 instance (I assume it is a problem with "wrong" data in our database, but I might be wrong):
c8baa johndoe - 2018-03-22T12:34:46+00:00 INFO (6): Tinebase_Server_WebDAV::handle::106 Starting to handle WebDAV request ( requestUri:/principals/users/986691f61f9daa5f97f37634fb83ca4e34b41365/ PID: 34)
The CalDAV client sends this request to the server:
This leads to to couple of notices stating that "Group/list principal does not exist" like this (for this specific request I got about 15 of those messages):
c8baa johndoe - 2018-03-22T12:34:46+00:00 NOTICE (5): Tinebase_WebDav_PrincipalBackend::getPrincipalByPath::176 Group/list principal does not exist: 645585e475809352e11c589e47f5dd25676a7712
What seems to kill the request in the end is this SabreDAV exception for the last notice:
Given I am not so deep involved in CalDAV and the implementation in Tine 2.0, I am wondering why those Group/list principal are read, especially since those are mostly internal groups from our LDAP instance that get synched into Tine 2.0. They are not related at all to certain events.
The ids mentioned above seem to be entries of the tine20_addressbook_lists table, those entries do still exist, and those lists have vaild members in the tine20_addressbook_list_members table. I did a quick check and could not find orphaned references in there. Not sure where the error is coming from or how to fix it.
Additional information: This issue is based on a "bug report" in the Tine 2.0 forum, see here https://www.tine20.org/forum/viewtopic.php?f=12&t=18756&p=68388
We recently moved from a very old 2016.* instance of Tine 2.0 to the 2018.02.1 version. All db migrations went fine. I kind of think that some checks within Tine 2.0 were hardened and maybe some references cannot be found any more. But not sure what and which.