Re: Is DAV:principal-property-search REPORT callable on any URL, as opposed to the DAV:principal-search-property-set REPORT?

Hello,

the server is Cyrus IMAP.  The use case is:

I want to create a meeting with attendee and the CUA is supposed to
display the freebusy information for the attendee.  While in theory the
Scheduling-Outbox should be used for this, in practice the CUA first
calls DAV:principal-property-search REPORT to get the calendar-user-
home-setS and on the resulting URLs a free-busy-query is sent.

To be precise, the CUA should get for the principal the calendar-user-
home-sets, and sent there free-busy-query, but it gets instead the
principal-URL and sends there the free-busy-query.  I guess some CalDAV
implementations do not differentiate between principal-URL, calendar-
home-set, or default calendar, therefore this logic apparently works
somewhere:
https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/302

So I do not know, whether the server or the client shall be fixed on
which URL DAV:principal-property-search REPORT shall be called.

Greetings
  Дилян


On Mon, 2021-03-01 at 09:21 +0100, Julian Reschke wrote:
> Am 01.03.2021 um 09:13 schrieb Дилян Палаузов:
> > Hello,
> > 
> > a client (Gnome Evolution) is calling DAV:principal-property-search
> > REPORT on an arbitrary URL (not included in DAV:principal-collection-
> > set) but containing <apply-to-principal-collection-set/>.
> > 
> > The server does not allow this, as the request URL is not in
> > DAV:principal-collection-set.
> > 
> > So the question is whether I shall work on the client or on the
> > server.
> > 
> > Greetings
> >    Дилян
> 
> Hard to say.
> 
> What is the server? What is your goal beyond this concrete question?
> 
> As far as I can tell, WebDAV ACL has no implementations that are still
> maintained, used, and interoperable, and thus can be considered dead.
> (And if that's not the case, I'd love to find out :-).
> 
> Best regards, Julian
>

Received on Monday, 1 March 2021 08:37:29 UTC