Re: [Evolution] caldav-sync - timespan



On Mon, 2015-06-08 at 13:52 +0200, Kohlen wrote:
And a bit later:
 > REPORT 
/owncloud/remote.php/caldav/calendars/matthias/kalendermemotoo/ 
HTTP/1.1
 > Soup-Debug-Timestamp: 1433758584
 > Soup-Debug: SoupSessionSync 1 (0x7f91e26bf220), SoupMessage 6 
(0x7f9198004f50), SoupSocket 7 (0x7f91980067a0)
 > Host: xxxxx
 > User-Agent: Evolution/3.12.10
 > Depth: 1
 > Content-Type: application/xml
 > Connection: close
 > Authorization: Basic [xxxxx:**********]
 >
 > <C:calendar-query xmlns:C="urn:ietf:params:xml:ns:caldav" 
xmlns:D="DAV:">
 >   <D:prop>
 >     <D:getetag/>
 >   </D:prop>
 >   <C:filter>
 >     <C:comp-filter name="VCALENDAR">
 >       <C:comp-filter name="VEVENT"/>
 >     </C:comp-filter>
 >   </C:filter>
 > </C:calendar-query>

< HTTP/1.1 7 Connection terminated unexpectedly
< Soup-Debug-Timestamp: 1433758674
< Soup-Debug: SoupMessage 6 (0x7f9198004f50)


(evolution-calendar-factory:16465): e-cal-backend-caldav-WARNING **: 
Server did not response with 207, but with code 7 (Connection 
terminated 
unexpectedly)
CalDAV - finished syncing with 56 items in a cache
[...]

This seems to be the cause of the problem. Any hints to solve this?

        Hi,
unfortunately no. It looks like your ownCloud server doesn't like the
generic search filter. Try to find out the server logs and see what's
written there. The server doesn't return much clues.

I tried with my ownCloud instance and it survives without any issue,
bot after start and after the Refresh invocation.
        Bye,
        Milan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]