View Issue Details

IDProjectCategoryView StatusLast Update
0003161SOGoBackend Calendarpublic2016-12-15 14:37
Reporterdmitry.nezhevenko Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Platform[Server] LinuxOSDebianOS Version7 (Wheezy)
Product Version2.2.17 
Summary0003161: Blackbery 10 can't edit event that was posted by KOrganizer (CalDAV)
Description

Hi,

I've just tried to create event using KDE Korganizer (configured to use SOGo CalDAV):

Apr 01 14:31:31 sogod [4903]: 127.0.0.1 "PUT /SOGo/dav/USER/Calendar/personal/1427887891.R264.ics HTTP/1.0" 401 0/3423 0.002 - - 0
Apr 01 14:31:32 sogod [4903]: 127.0.0.1 "PUT /SOGo/dav/USER/Calendar/personal/1427887891.R264.ics HTTP/1.0" 201 0/3423 0.115 - - 16K
Apr 01 14:31:32 sogod [4903]: 127.0.0.1 "GET /SOGo/dav/USER/Calendar/personal/1427887891.R264.ics HTTP/1.0" 401 0/0 0.002 - - 0
Apr 01 14:31:32 sogod [4903]: 127.0.0.1 "GET /SOGo/dav/USER/Calendar/personal/1427887891.R264.ics HTTP/1.0" 200 887/0 0.011 3421 74% 0

Later once event appeared on BB10 phone I've tried to edit it using smartphone:

Apr 01 14:32:15 sogod [4907]: 127.0.0.1 "REPORT /SOGo/dav/USER/Calendar/personal/ HTTP/1.0" 207 12473/328 0.016 - - 0
Apr 01 14:32:16 sogod [4907]: 127.0.0.1 "PUT /SOGo/dav/USER/Calendar/personal/c6f6f5f0-486e-4a6f-b60d-e30047922bcc.ics HTTP/1.0" 403 196/899 0.010 - - 0

Event was not changed in SOGO web (and KOrganizer).

I don't know why bb10 sends REPORT request before PUT. Maybe it tries to find proper URL to post. (see additional info for request). In any case it looks like bb10 tries to use 'filename' from event itself instead of original one.

UID:c6f6f5f0-486e-4a6f-b60d-e30047922bcc

Additional Information

=== REPORT (from BB10) ===

REPORT /SOGo/dav/USER/Calendar/personal/ HTTP/1.0
Host: --
Accept-Encoding: identity
Content-Length: 328
Content-Type: text/xml;charset=utf-8
depth: 1
authorization: Basic ---
User-Agent: RIM
x-webobjects-server-url: --
x-webobjects-server-port: 443
x-webobjects-server-name: --
X-Forwarded-For: 127.0.0.1
X-Host: --
X-Forwarded-Proto: https

<ns0:calendar-query xmlns:ns0="urn:ietf:params:xml:ns:caldav" xmlns:ns1="DAV:"><ns1:prop><ns1:getetag /></ns1:prop><ns0:filter><ns0:comp-filter name="VCALENDAR"><ns0:comp-filter name="VEVENT"><ns0:time-range end="20160331T000000Z" start="20140401T000000Z" /></ns0:comp-filter></ns0:comp-filter></ns0:filter></ns0:calendar-query>

Response contains '/SOGo/dav/USER/Calendar/personal/1427887891.R264.ics'.

=== PUT ===

PUT /SOGo/dav/USER/Calendar/personal/c6f6f5f0-486e-4a6f-b60d-e30047922bcc.ics HTTP/1.0
Host: --
Accept-Encoding: identity
Content-Length: 885
Content-Type: text/calendar; charset="utf-8"
authorization: --
User-Agent: RIM
x-webobjects-server-url: --
x-webobjects-server-port: 443
x-webobjects-server-name: --
X-Forwarded-For: 127.0.0.1
X-Host: --
X-Forwarded-Proto: https

Response 403:
<?xml version="1.0" encoding="ISO-8859-1"?>
<html xmlns="http://www.w3.org/1999/xhtml&quot;>
<body><h3>An error occurred during object publishing</h3><p>Event UID already in use. ()</p></body>
</html>

PS: I have not read CardDAV RFC fully, but it looks like 'event UID already in use' should be machine-readable:

            &lt;!ELEMENT no-uid-conflict (DAV:href)>

(https://tools.ietf.org/html/rfc4791#page-26)

TagsNo tags attached.

Activities

ludovic

ludovic

2016-12-15 14:37

administrator   ~0011000

Lowering because we have no testing device.

Issue History

Date Modified Username Field Change
2015-04-01 08:03 dmitry.nezhevenko New Issue
2016-12-15 14:37 ludovic Note Added: 0011000
2016-12-15 14:37 ludovic Severity major => minor