Hi,
It seems that Android client CalDAV-Sync/0.4.32 periodically issues PROPFIND requests to the configured DAViCal server, but with different paths.
The DAViCal server is configured as https://davical.squirrel.nl/caldav.php/, but other paths used are:
/remote.php/caldav/ /owncloud/remote.php/caldav/ /groupdav.php/
Is this normal behaviour?
-- Johan
Hi Johan,
that's currently normal procedure of CalDAV-Sync. It periodically scans the server for new calendars and task lists to sync. Currently it does that using the same routine that it uses during the initial account setup.
The account setup routine scans various known paths to find all principals paths your account has access to and all calendar-home paths that belong to them. The easiest way to keep the calendar list updated was to run the same routine every now and then. We're probably going to improve that in future versions and store the principal home path to we can skip this "discovery" step.
I hope that helps.
Cheers,
Marten
Am 20.02.20 um 15:13 schrieb Johan Vromans:
Hi,
It seems that Android client CalDAV-Sync/0.4.32 periodically issues PROPFIND requests to the configured DAViCal server, but with different paths.
The DAViCal server is configured as https://davical.squirrel.nl/caldav.php/, but other paths used are:
/remote.php/caldav/ /owncloud/remote.php/caldav/ /groupdav.php/
Is this normal behaviour?
-- Johan
Hi Marten,
On Fri, 21 Feb 2020 11:43:24 +0100, Marten Gajda marten@dmfs.org wrote:
that's currently normal procedure of CalDAV-Sync.
Ok, I see.
It caught my attention when I noticed the owncloud urls. I have replaced ownCloud by Nextcloud last year and wondered whether I forgot to update some settings.
Thanks, Johan