You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of Evolution backed by cyrus-imapd CalDAV, I want to schedule a meeting with another user as attendee of this meeting. After having provided an email address of the other user, evolution then asks cyrus-imapd CalDAV on my behalf regarding data of the other user, in preparation of obtaining freebusy data of that other user. Cyrus-imapd CalDAV is expected to answer properly, but instead replies with an error.
However, instead of that, cyrus-imapd CalDAV searches the handler for "principal-property-search" reports in a list defined in file imap/http_caldav.c:
Observe that there is an overlap of supported report types ("expand-property" is supported by both report lists), but the report type "principal-property-search" is not among them. That is why cyrus-imapd CalDAV does not process "principal-property-search" properly, while it could.
Is there a reason not to include the support for "principal-property-search" in file "imap/http_caldav.c"?
If not, then fixing this bug could allow users of Evolution (and potentially other clients) to actually see freebusy information of other invitees.
The text was updated successfully, but these errors were encountered:
The mailing lists archives, where WebDAV was discussed, are lost.
As far as I remember it is not clear where to send this REPORT request.
This is tracked on Evolution side at https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/302 . There the REPORT is sent towards the principal-url, while in your snippet it is sent towards the calendar. This might be consequence of the fact that you have setup the calendar as „New calendar“ with CalDAV url instead of using “Collection account”.
As stated there, I have implemented apply-to-principal-collection-set in the way I understand it. However this was towards Cyrus 3.4, it was a big change, or alike and I have not forward-copied this change on my system to newer versions. I could upload here my patches, if somebody wants to work on these.
Somehow Evolution and Cyrus IMAP do not agree how to send the free-busy information from the Scheduling Outbox. I have forgotten the details.
Is there a reason not to include the support for "principal-property-search" in file "imap/http_caldav.c"?
Probably because RFC 3744 says this needs to sent to the principal home url - /dav/principals/user/abc.
As a user of Evolution backed by cyrus-imapd CalDAV, I want to schedule a meeting with another user as attendee of this meeting. After having provided an email address of the other user, evolution then asks cyrus-imapd CalDAV on my behalf regarding data of the other user, in preparation of obtaining freebusy data of that other user. Cyrus-imapd CalDAV is expected to answer properly, but instead replies with an error.
How to reproduce
Expected result
Actual result
Analysis
Cyrus-imapd CalDAV should search and find the handler for "principal-property-search" reports in a list defined in file imap/http_dav.c:
However, instead of that, cyrus-imapd CalDAV searches the handler for "principal-property-search" reports in a list defined in file imap/http_caldav.c:
Observe that there is an overlap of supported report types ("expand-property" is supported by both report lists), but the report type "principal-property-search" is not among them. That is why cyrus-imapd CalDAV does not process "principal-property-search" properly, while it could.
Is there a reason not to include the support for "principal-property-search" in file "imap/http_caldav.c"?
If not, then fixing this bug could allow users of Evolution (and potentially other clients) to actually see freebusy information of other invitees.
The text was updated successfully, but these errors were encountered: