634898 - OPTION method is run on calendar home instead of configured calendar

Status: RESOLVED DUPLICATE of bug 610087

(Calendar :: Provider: CalDAV, defect)

Description

[Arnaud Quillaud]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7

The first request done by Lightning is a PROPFIND on the configured calendar url.

The second request is an OPTION on what is assumed (1 level up from calendar url) as the corresponding calendar home collection. From what I can see, this is only used to check the DAV header for "calendar-auto-schedule". I dont see any reason why we need to issue this command on the calendar home collection as opposed to the configured calendar collection.

This behavior is problematic because the logged in user may have read privilege on the calendar collection but no privilege on the calendar home collection. 

Reproducible: Always

Comment 1

[Wim Lewis]

Is this the same as Bug 658960 - Incorrect url to HTTP OPTIONS request ?

Comment 2

[Philipp Kewisch [:Fallen][☁️📆]]

Wim, before I forget to mention, thanks for doing such an elaborate search for duplicates when filing bug 674088!

This sounds very duplicate, marking as such.

Comment 3

[Arnaud Quillaud]

Well this may still end up being a duplicate but the symptoms are different as far as I can see.
What I'm seeing is an OPTION request being made one level up from the configured calendar url, not at the root (see function caldav_setCalHomeSet() in calDavCalendar.js).
In other words, assuming a configured calendar url of http://example.com/caldav/calendar/ , I'm seing a request being made on http://example.com/caldav/ , not on http://example.com/ as described in bug 674088 and bug 658960 .
This OPTIONS command is necessary to check whether the server supports scheduling but the same check could well be done directly against the configured calendar url.

Comment 4

[Stefan Fleiter (:sfleiter)]

Same as bug 610087 and bug 588799.