Re: How to determine if a collection can be DELETEd?

> How to communicate to the WebDAV client which are deletable?

For WebDAV on a files folder the PROPFIND returns a status to indicate
what will return when open the resource.
Maybe this can be reused somehow,
In general we need to have linux permissions as the NextCloud has
<oc:permissions/>
https://docs.nextcloud.com/server/latest/developer_manual/client_apis/WebDAV/basic.html#supported-properties

Basically other WebDAV clients needs this so check how it's implemented there
On Sun, Sep 29, 2024 at 12:49 PM Дилян Палаузов
<dilyan.palauzov@aegee.org> wrote:
>
> Hello,
>
> how can a WebDAV client determine, if a collection can be deleted, so that it shows or hides a Delete button to the user?
>
> How is the Allow: header different from DAV:supported-method-set?  Does the former return results irrespective of the authentication state, but the latter
> • includes OPTIONS
> • possibly includes MOVE, and
> • considers the authentication state?
>
> WebDAV Access Control Protocol RFC says DELETE can be performed on collection, only if the parent has unbind privilege.  But the CalDAV’s Default calendar and the Scheduling Inbox collections cannot be deleted.  They can exist in the calendar-home-set collection, together with other, deletable calendars.  So the calendar-home-set must have unbind privilege, as some of its descendant can be deleted.  How to communicate to the WebDAV client which are deletable?
>
> Greetings
>   Дилян
>
> DAV:supported-method-set — https://www.rfc-editor.org/rfc/rfc3253#section-3.1.3
> HTTP Allow header — https://www.rfc-editor.org/rfc/rfc7231#section-7.4.1
> Unbind and DELETE — https://www.rfc-editor.org/rfc/rfc3744.html#appendix-B
> CalDAV Default Calendar Collection — https://www.rfc-editor.org/rfc/rfc6638.html#section-4.3
>

Received on Sunday, 29 September 2024 18:50:38 UTC