[GH-ISSUE #139] Bad url construction when multiples calendar-home-set. #136

New issue

Closed

opened 2026-02-25 20:30:58 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 20:30:58 +03:00

Owner

Originally created by @flechilla on GitHub (Jun 9, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/139

If the principal has multiple DAV:calendar-home-set, so the server returns something like this:
<C:calendar-home-set xmlns:C="urn:ietf:params:xml:ns:caldav" xmlns:D="DAV:"> <D:href>/collections/users/aff31/</D:href> <D:href>/collections/groups/public/</D:href> </C:calendar-home-set>
So the client concatenate the href of calendar-home-set, so it makes a request to the url
PROPFIND /collections/users/aff31//collections/groups/public/ HTTP/1.1.
It should not be like that, it should perfoms the PROFIND method to the hrefs in different requests.

Originally created by @flechilla on GitHub (Jun 9, 2016). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/139 If the principal has multiple DAV:calendar-home-set, so the server returns something like this: `<C:calendar-home-set xmlns:C="urn:ietf:params:xml:ns:caldav" xmlns:D="DAV:"> <D:href>/collections/users/aff31/</D:href> <D:href>/collections/groups/public/</D:href> </C:calendar-home-set>` So the client concatenate the href of calendar-home-set, so it makes a request to the url `PROPFIND /collections/users/aff31//collections/groups/public/ HTTP/1.1`. It should not be like that, it should perfoms the PROFIND method to the hrefs in different requests.

kerem closed this issue

2026-02-25 20:30:58 +03:00

kerem commented

2026-02-25 20:30:59 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 10, 2016):

What server are you using? Never seen that but should be fixed if this is valid of course.

@aluxnimm commented on GitHub (Jun 10, 2016): What server are you using? Never seen that but should be fixed if this is valid of course.

kerem commented

2026-02-25 20:30:59 +03:00

Author

Owner

@flechilla commented on GitHub (Jun 13, 2016):

I'm using my own server implementation. That doesn't matters because my server is returning the response that I mention before, which is OK. Maybe you haven't seen the bug before because the principal that you have tried doesn't have more than 1 calendar-home.
Sorry for not reply before.

@flechilla commented on GitHub (Jun 13, 2016): I'm using my own server implementation. That doesn't matters because my server is returning the response that I mention before, which is OK. Maybe you haven't seen the bug before because the principal that you have tried doesn't have more than 1 calendar-home. Sorry for not reply before.

kerem commented

2026-02-25 20:30:59 +03:00

Author

Owner

@evert commented on GitHub (Jun 13, 2016):

The issue itself is valid from a CalDAV protocol perspective, but also almost nobody actually supports multiple calendar homes (I don't know anyone who does).

@evert commented on GitHub (Jun 13, 2016): The issue itself is valid from a CalDAV protocol perspective, but also almost nobody actually supports multiple calendar homes (I don't know anyone who does).

kerem commented

2026-02-25 20:30:59 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 13, 2016):

ok thx for clarification. so for Autodiscovery we should check all available home-sets.

@aluxnimm commented on GitHub (Jun 13, 2016): ok thx for clarification. so for Autodiscovery we should check all available home-sets.

kerem commented

2026-02-25 20:30:59 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 15, 2016):

fix will be in next release.

@aluxnimm commented on GitHub (Jun 15, 2016): fix will be in next release.

kerem commented

2026-02-25 20:30:59 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 25, 2016):