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
Agendav apparently grants the WebDAV ACLs successfully when used with DAViCal. Before granting ACLs AgentDAV calls REPORT DAV:principle-property-search on the “base URL”, which is for Cyrus, due the lack of better ideas, server/dav/calendars.
In Cyrus REPORT DAV:principle-property-search works only when called on /dav/principals, it does not work on /dav/principals/user/x (the DAV:current-user-principal result) nor on /dav/calendars.
How is a WebDAV client supposed to discover the /dav/principals/ address, towards which REPORT DAV:principle-property-search can be called?
Is it wrong to do it like DAViCal and allow the REPORT on /dav/calendars/?
The text was updated successfully, but these errors were encountered:
Agendav apparently grants the WebDAV ACLs successfully when used with DAViCal. Before granting ACLs AgentDAV calls REPORT DAV:principle-property-search on the “base URL”, which is for Cyrus, due the lack of better ideas, server/dav/calendars.
In Cyrus REPORT DAV:principle-property-search works only when called on /dav/principals, it does not work on /dav/principals/user/x (the DAV:current-user-principal result) nor on /dav/calendars.
How is a WebDAV client supposed to discover the /dav/principals/ address, towards which REPORT DAV:principle-property-search can be called?
Is it wrong to do it like DAViCal and allow the REPORT on /dav/calendars/?
The text was updated successfully, but these errors were encountered: