Skip to content

Conversation

@raimund-schluessler
Copy link
Member

@raimund-schluessler raimund-schluessler commented Jul 18, 2021

This allows to set headers for requests on dav objects. Specifically needed to move objects without creating a trash bin entry before this is fixed in server. Unfortunately, the server does not seem to respect the header X-NC-CalDAV-No-Trashbin for dav objects.

Related to nextcloud/tasks#1685 and nextcloud/calendar#3325

@tcitworld
Copy link
Member

Is there an issue in server for X-NC-CalDAV-No-Trashbin not being respected?

@raimund-schluessler
Copy link
Member Author

raimund-schluessler commented Jul 18, 2021

Is there an issue in server for X-NC-CalDAV-No-Trashbin not being respected?

I would think so, but I haven't had a look yet (and I don't know the server code well).

Edit: For calendars, it is respected. When I don't send it, the calendar is not deleted, even though it is in the trash bin already. For calendar objects, this is different. If the object is in the trash bin, it is deleted on request, no matter if the X-NC-CalDAV-No-Trashbin header is set or not. And it is always put in the trash bin, even with the header present.

Signed-off-by: Raimund Schlüßler <[email protected]>
Signed-off-by: Richard Steinmetz <[email protected]>
@st3iny st3iny force-pushed the enh/noid/dav-object-headers branch from 82c0d19 to acfa605 Compare August 10, 2021 08:09
Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure :)

(sorry, still processing a long backlog of notifications after vacation)

@raimund-schluessler raimund-schluessler merged commit 935b151 into master Aug 13, 2021
@delete-merged-branch delete-merged-branch bot deleted the enh/noid/dav-object-headers branch August 13, 2021 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants