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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13123
------------------------------------------------------------------------------
  Ticket             | 13123
  Created By         | amessina at messinet.com
  Summary            | Horde/Kronolith/CalDAV: events modified more than once
                     | don't sync via CalDAV
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_5_1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


amessina at messinet.com (2014-04-17 21:00) wrote:

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.



amessina at messinet.com (2014-04-17 21:00) uploaded:  
horde-webdav-modification-issue.txt

http://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=horde-webdav-modification-issue.txt&ticket=13123&fn=%2Fhorde-webdav-modification-issue.txt