SOGo | BTS

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001853SOGoBackend Calendarpublic2012-06-27 10:202012-06-27 12:10
Reporterjraby 
Assigned Tojraby 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version1.3.16 
Target VersionFixed in Version 
Summary0001853: Handling of events with the same UID but different filenames
DescriptionCurrently, 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 [^]

Additional InformationTo 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0004092)
jraby (viewer)
2012-06-27 12:10
edited on: 2013-11-18 11:49

fixed: https://github.com/inverse-inc/sogo/commit/e587ae08cfb3d525200ba3365c4ee9d961475d66 [^]


- Issue History
Date Modified Username Field Change
2012-06-27 10:20 jraby New Issue
2012-06-27 12:10 jraby Note Added: 0004092
2012-06-27 12:10 jraby Assigned To => jraby
2012-06-27 12:10 jraby Status new => resolved
2012-06-27 12:10 jraby Resolution open => fixed
2013-11-18 11:49 francis Note Edited: 0004092 View Revisions


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker