Re: CalDAV REPORT/Multi-Status problem

[email protected]
Newsgroups gmane.comp.horde.kronolith
Message-ID <[email protected]>
Zitat von Jan Schneider <[email protected]>:

> Zitat von [email protected]:
>
>> Hello,
>>
>> we try to get a CRM Application to use the Horde/Kronolith calender  
>> with CalDAV. The CRM refuses to do something useful and throw a  
>> error about Multi-Status. On the wire we got something like this:
>>
>> Client:
>>
>> REPORT /rpc.php/calendars/lst_hoe/calendar:x4oABU6jTahP5FEW0nglG3A/  
>> HTTP/1.1\r\n
>>
>> With this data
>>
>> <?xml version="1.0"?>
>> <C:calendar-query xmlns:C="urn:ietf:params:xml:ns:caldav">
>>    <D:prop xmlns:D="DAV:">
>>        <D:getetag/>
>>        <C:calendar-data>
>>            <C:comp name="VCALENDAR"/>
>>        </C:calendar-data>
>>    </D:prop>
>>    <C:filter>
>>        <C:comp-filter name="VCALENDAR">
>>            <C:comp-filter name="VEVENT">
>>                <C:time-range end="20140820T105557Z"  
>> start="20140218T200121Z"/>
>>                <C:prop-filter name="STATUS">
>>                    <C:text-match caseless="yes"  
>> collation="i;ascii-casemap">TENTATIVE</C:text-match>
>>                </C:prop-filter>
>>            </C:comp-filter>
>>        </C:comp-filter>
>>    </C:filter>
>> </C:calendar-query>
>>
>>
>> Server (Horde) response:
>>
>> HTTP/1.1 207 Multi-Status\r\n
>>
>> <?xml version="1.0" encoding="utf-8"?>
>> <d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"  
>> xmlns:cal="urn:ietf:params:xml:ns:caldav"  
>> xmlns:cs="http://calendarserver.org/ns/"  
>> xmlns:card="urn:ietf:params:xml:ns:carddav"/>
>>
>>
>> The client is confused with this and give up. Is it a client error  
>> to not first issue a PROPFIND like for example  
>> Thunderbird/Lightning does or what could be the problem?
>>
>> Thanks for any help
>>
>> Andreas
>
> There is nothing wrong with the response. The query doesn't return  
> any results, so the response is empty too.
>

I suspected problems with empty response and created some events in  
the matching timeframe, but it also filters for STATUS=TENTATIVE, no?  
This would mean no STATUS=CONFIRMED which looks bogus to me...

Thanks

Andreas


-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.