SOGo - BTS - SOGo
View Issue Details
0001853SOGoBackend Calendarpublic2012-06-27 10:202012-06-27 12:10
jraby 
jraby 
normalminorhave not tried
resolvedfixed 
1.3.16 
 
0001853: Handling of events with the same UID but different filenames
Currently, if a PUT is made for a new event that uses the same UID as an existing event, sogo will accept the new event and both events will show up in the user's calendar.

As per rfc4791 (section 5.3.2.1), this is wrong: the server should return a 403 with the appropriate error - CALDAV:no-uid-conflict.


see http://www.ietf.org/rfc/rfc4791.txt [^]

To reproduce,

1. Create an event using sogo web
2. Fetch the created event using a dav client (cadaver)
3. rename the fetched file to something.ics
4. PUT the renamed file on the server.

SOGo will accept it event if the UID conflicts with an existing event.
No tags attached.
Issue History
2012-06-27 10:20jrabyNew Issue
2012-06-27 12:10jrabyNote Added: 0004092
2012-06-27 12:10jrabyAssigned To => jraby
2012-06-27 12:10jrabyStatusnew => resolved
2012-06-27 12:10jrabyResolutionopen => fixed
2013-11-18 11:49francisNote Edited: 0004092bug_revision_view_page.php?bugnote_id=4092#r20

Notes
(0004092)
jraby   
2012-06-27 12:10   
(edited on: 2013-11-18 11:49)
fixed: https://github.com/inverse-inc/sogo/commit/e587ae08cfb3d525200ba3365c4ee9d961475d66 [^]