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

[Anthony Messina]

On Thursday, April 17, 2014 16:08:56 Anthony Messina wrote:
> I've submitted the following as http://bugs.horde.org/ticket/13123
> 
> 
> 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.
> 
> Any help in resolving this issue would be appreciated.  Thanks.  -A

Well, I'm a day behind.  That's what vacation can do to you!  This was 
reported previously as http://bugs.horde.org/ticket/13113 and is marked 
resolved.

Thanks.  -A

-- 
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.horde.org/archives/horde/attachments/20140417/dcbf7727/attachment.bin>