Tickets :: [#13123] Horde/Kronolith/CalDAV: events modified more than once don't sync via CalDAV

Summary	Horde/Kronolith/CalDAV: events modified more than once don't sync via CalDAV
Queue	Horde Framework Packages
Queue Version	FRAMEWORK_5_1
Type	Bug
State	Duplicate
Priority	1. Low
Owners
Requester	amessina (at) messinet (dot) com
Created	04/17/2014 (4097 days ago)
Due
Updated	04/17/2014 (4097 days ago)
Assigned
Resolved	04/17/2014 (4097 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/17/2014 11:21:41 PM	Michael Rubinsky	Comment #2 State ⇒ Duplicate Priority ⇒ 1. Low	Reply to this comment
~~Bug: 13113~~

04/17/2014 09:00:58 PM	amessina (at) messinet (dot) com	Comment #1 Priority ⇒ 2. Medium New Attachment: horde-webdav-modification-issue.txt Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Framework Packages Summary ⇒ Horde/Kronolith/CalDAV: events modified more than once don't sync via CalDAV Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
Using Horde 5.1.6, Kronolith 4.1.5, and Horde_Dav 1.0.4 after an event is created and then modified more than once, the event is no longer synced via CalDAV. The issue appears to be that after the second modification, the ETag and Last-Modified headers are not updated with the newer event_modified timestamp. I have attached a text file with the instructions to reproduce this issue, as well as examples of the HTTP headers detailing the ETag and Last-Modified headers not being updated after the second modification.