CalDAV and Nextcloud: 404 on all but One Account when Setup for Multiple Accounts

[stellarpower]

Hi,

Am using tasks with a nextcloud instance - had set up CalDAV some time ago, but had problems with syncing that only just managed to look into.

As it's a system I manage myself, I have multiple accounts on the nextcloud - and so, had set up tasks for multiple users using the CalDAV backend. The system is low-power, so sometimes I get problems with syncing in general, but when I have one account that is syncing cleanly, I noticed that the others fail, and if I go into the settings for those others, it seems they have all 404ed.

Bringing up the DAV URL in a private windows in my browser, if I log in as one user, then try to access the calendar DAV URL for a different user, I will get a 404 - even though the URL is correct, once I have authenticated I can then only see the calendars for that user, and nextcloud is returning this as a 404 rather than a 401 for whatever reason. This leads me to believe that the CalDAV backend might be applying credentials or somehow grouping web requests on a per-domain basis, rather than a per-account basis, and thus, the first that syncs correctly wins out, but the other accounts I have can't sync, as the URL is not valid for the user form the first.

LMK what additional details might be helpful, not sure how easily I could produce an MRE, it might just be that my server is the problem here, but I thought if this is what it smells like to me, it might be immediately clear from the source code that either this is a scenario that hadn't been fully-handled or it's something on my end / with my NC.

Thanks!

[abaker]

Cookies were stored by URL, so adding a second account on the same server would overwrite cookies from the first account, causing the 404 error. This should be fixed in 1d58292

[stellarpower]

Awesome, that was fast. Thank you!! 7 May 2023 17:12:13 Alex Baker ***@***.***>:

…

Closed #2301[#2301] as completed. — Reply to this email directly, view it on GitHub[#2301 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABGF2AIWFECXFA2NVT76EGTXE7CV3ANCNFSM6AAAAAAXYNKAXU]. You are receiving this because you authored the thread.[Tracking image][https://github.com/notifications/beacon/ABGF2AJXOSUI3GMDWL6KTLTXE7CV3A5CNFSM6AAAAAAXYNKAXWWGG33NNVSW45C7OR4XAZNWJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XKUY3PNVWWK3TUL5UWJTYAAAAAEI3RG7CQ.gif]