Skip to content

fix(dav): return RFC 4791 no-uid-conflict on duplicate calendar UID#61659

Open
SebastianKrupinski wants to merge 1 commit into
masterfrom
fix/dav-report-uid-conflict
Open

fix(dav): return RFC 4791 no-uid-conflict on duplicate calendar UID#61659
SebastianKrupinski wants to merge 1 commit into
masterfrom
fix/dav-report-uid-conflict

Conversation

@SebastianKrupinski

@SebastianKrupinski SebastianKrupinski commented Jun 29, 2026

Copy link
Copy Markdown
Contributor
  • Resolves: #

Summary

  • Original Community PR: fix(dav): return RFC 4791 no-uid-conflict on duplicate calendar UID #61640
  • Modified the CalDAV and CardDAV backend create to use new serializable exception type that returns a dav response as per RFC
  • Modified the CalDAV and CardDAV backend move to use new serializable exception type that returns a dav response as per RFC
  • RFC 4791 (CalDAV) defines the CALDAV:no-uid-conflict precondition. It ensures that within a calendar collection, there cannot be two different resources containing iCalendar objects with the same UID.
  • RFC 6352 (CardDAV) defines the analogous CARDDAV:no-uid-conflict precondition for address books. It ensures that within an address book collection, there cannot be two different vCard resources with the same UID.

Checklist

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

Signed-off-by: Nico Donath <ndo84bw@gmx.de>
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
@SebastianKrupinski

Copy link
Copy Markdown
Contributor Author

/backport to stable34

@SebastianKrupinski

Copy link
Copy Markdown
Contributor Author

/backport to stable33

@SebastianKrupinski

Copy link
Copy Markdown
Contributor Author

/backport to stable32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: 🏗️ In progress

Development

Successfully merging this pull request may close these issues.

2 participants