User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:126.96.36.199) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Lightning 0.9pre Build 2008072818
I have apple caldav server setup running on FreeBSD. I use this to store all my calendars. Under Lighting 0.8 I could view each of my calendars. Under 0.9pre the calendars don't apear. The error reported is multiple of:
Warning: There has been an error reading data for calendar: CIS. However, this error is believed to be minor, so the program will attempt to continue. Error code: DAV_NOT_DAV. Description: The resource at http://calendar.clearchain.com/calendars/users/benjsc/CIS is either not a DAV collection or not available
I understand debugging remote calendars is hard so please email me direct and I'll give the developer assigned to this bug username/pass and access to server logs for debugging.
Steps to Reproduce:
1. Setup calendar to above address
2. Deinstall lightning 0.8
3. Install lighting 0.9pre
4. Start thunderbird
The calendars show up in the left column (ie remembers there is calendars) however no data about the calendars is displayed
The data for the calendar is usable
I can take a look at this.
Login details provided to Bruno
Created attachment 331706 [details] [diff] [review]
ensure trailing slash on initial PROPFIND
The patch in bug 447913 left us doing the initial PROPFIND against the user-supplied calendar URL, without ensuring that it had a trailing slash. CalendarServer reacts poorly to calendar URLs lacking a trailing slash.
Checked in on HEAD and MOZILLA_1_8_BRANCH
Repeating with the latest nightly confirms the fix is successful - Thanks!
You folk have done a nice job since 0.8 - looks and works great!
Don't work for me
the build 2008073119 can not get my events
the build 2008072919 can get my events
on 2008073119 I get the error DAV_NOT_DAV ....
(In reply to comment #6)
> Don't work for me
> the build 2008073119 can not get my events
> the build 2008072919 can get my events
> with Davical
That 31 July build does work for me with current davical, on Linux. Any chance you could turn on two prefs calendar.debug.log and calendar.debug.log.verbose and report what you see in the error console?
(In reply to comment #8)
CalDAV: Status 207 on initial PROPFIND for calendar mdelorme
CalDAV: Authentication scheme Basic
CalDAV: recv: <?xml version="1.0" encoding="utf-8" ?>
<status>HTTP/1.1 200 OK</status>
Avertissement : There has been an error reading data for calendar: mdelorme. However, this error is believed to be minor, so the program will attempt to continue. Error code: DAV_NOT_DAV. Description: The resource at https://www.tennaxia.net/cal/mdelorme/home/ is either not a DAV collection or not available
Avertissement : There has been an error reading data for calendar: mdelorme. However, this error is believed to be minor, so the program will attempt to continue. Error code: READ_FAILED. Description:
[In reply to comment #9]
This looks like a DAViCal problem parsing the getctag query. On my DAViCal setup the getctag part of that response looks like
<status>HTTP/1.1 404 Not Found</status>
... whereas yours just repeats back the query. What version of DAViCal are you using?
... and mine is 0.9.5 IMO the remaining problem here is a DAViCal one rather than a Sunbird/Lightning one. Is it possible for you to upgrade?
Unfortunately The upgrade is not planned, so I can't upgrade
Since we're working with the current version of DAViCal, I'm going to go ahead and re-close this bug. Will suggest a relnote about interop issues with older versions of DAViCal. Sorry for your trouble, Maxime; hope they will plan an upgrade soon.
Bruno, I need a good descriptive relnote-text for this bug (see comment 14).
(In reply to comment #15)
> Bruno, I need a good descriptive relnote-text for this bug (see comment 14).
> Any suggestions?
I'd suggest something along the lines of "There are interoperability issues with versions of DAViCal (RSCDS) prior to 0.9.5. People using earlier releases of DAViCal are advised to stay with Sunbird/Lightning 0.8 until they can upgrade their DAViCal to the current version."
We have the same issue within our company and discovered we can work around it by renewing the calendars, only this time as an iCal calendar! Until we didn't find any problems...