Free/Busy info is not shown with Kolab groupware servers (iRony CalDAV server)

UNCONFIRMED
Unassigned

Status

defect
UNCONFIRMED
5 years ago
2 years ago

People

(Reporter: pkou, Unassigned)

Tracking

Lightning 3.3

Details

()

Reporter

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36

Steps to reproduce:

Prerequisite:
 - Latest stable Kolab is installed from http://kolab.org/, or just iRony CalDAV server from https://git.kolab.org/iRony/tag/?id=iRony-0.2.7
 - An account for john.doe@example.org and test@example.org is created at the server

Steps:
 - Create new calendar A in Lightning that connects to iRony CalDAV server using URL http://kolab-dav/calendars/john.doe@example.org/
 - Create new calendar B in Lightning that connects to iRony CalDAV server using URL http://kolab-dav/calendars/test@example.org/
 - Create an appointment in calendar A for some time X
 - Try to create an appointment in calendar B, invite john.doe@example.org, and check his free/busy time


Actual results:

The free/busy information is not available.

Further investigation with the iRony team has shown the following issues:
a) Lightning double-escaping the principal URL in subsequent requests to CalDAV server: See https://issues.kolab.org/show_bug.cgi?id=3598#c2 for details

b) After the first issue fixed, Lightning does not request for free/busy info when the server supports the CalDAV option schedule-outbox-URL but when it does not support the option schedule-inbox-URL: See https://issues.kolab.org/show_bug.cgi?id=3598#c4 (and #c5) for details


Expected results:

The free/busy info shows that the user john.doe@example.org is busy at the time X

Comment 1

5 years ago
Does this occur with Lightning 3.3.1 as well?

If so, can you please enable the debug logging (set calendar.debug.log and calendar.debug.log.verbose to true at menu->options->options->general->advanced->config editor - if not existing, just add them) and provide the log (ctrl+shift+j) when reproducing the issue and the Lightning end.

Comment 2

3 years ago
This is still present in the current Lightning release 4.7
Duplicate of this bug: 1288385
You need to log in before you can comment on or make changes to this bug.