mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 11:05:56 +03:00
[GH-ISSUE #442] Incorrect "If-Match" header can lead to data loss #426
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#426
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lbuchs on GitHub (Jan 16, 2025).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/442
Outlook CalDav Synchronizer does not send the correct "If-Match" Header with a PUT request when modify a entry.
Steps to reproduce:
Now the CalDav Synchronizer does:
1.) A
REPORTrequest to the calendar:2.) The server responses with the e-tag
<d:getetag>"22222"</d:getetag>3.) CalDav Synchronizer does a
REPORTto get the new event data,4.) CalDav Synchronizer does a
PUTrequest to send the modified card (which is based on ETag "1111") to the Server. But in the header it uses the ETag fetched before:If-Match: "22222"5.) The Server should respond with
412 Precondition Failedbecause because the provided card is based on ETag"11111", but it gets overwritten with the changes of ETag"22222"lost.possible solution
When syncing,
PUTrequests should be made before fetching new data from the server.