Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support CalDAV auto-discovery #309

Open
thomaseizinger opened this issue Jun 1, 2024 · 1 comment
Open

Support CalDAV auto-discovery #309

thomaseizinger opened this issue Jun 1, 2024 · 1 comment

Comments

@thomaseizinger
Copy link

I am using fastmail which uses https://caldav.fastmail.com as their entrypoint for CalDAV. See https://www.fastmail.help/hc/en-us/articles/1500000278342-Server-names-and-ports#h_01H95ZZXYQJCB2E8CEM5PDK8H0 for details.

Plugging that into "Errands" didn't work, it resulted in a 404. Indeed, the above URL returns a 404 when contacted directly. Fastmail makes use of the CalDAV auto-discovery (outlined in https://datatracker.ietf.org/doc/html/rfc6764) which essentially says:

  1. Go to <host>/.well-known/caldav
  2. Take the re-direct returned (in fastmail's case: https://caldav.fastmail.com/dav/calendars)
  3. Use that as a base for caldav operations

Indeed, Errands correctly imports all tasks when the Server URL is set to https://caldav.fastmail.com/dav/calendars

@LunarWatcher
Copy link

Same situation with Baikal, but baikal requires https://caldav.{server}/dav.php/calendars/ because server differences. Would be more convenient to be able to use the base domain directly

@mrvladus mrvladus mentioned this issue Oct 10, 2024
48 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants