Closed
Bug 448453
Opened 15 years ago
Closed 15 years ago
Caldav Calenders working with 0.8 don't load under 0.9pre
Categories
(Calendar :: Provider: CalDAV, defect)
Calendar
Provider: CalDAV
Tracking
(Not tracked)
RESOLVED
FIXED
0.9
People
(Reporter: Benjamin.Close, Assigned: browning)
Details
Attachments
(1 file)
1.21 KB,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.1) 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. Reproducible: Always Steps to Reproduce: 1. Setup calendar to above address 2. Deinstall lightning 0.8 3. Install lighting 0.9pre 4. Start thunderbird Actual Results: The calendars show up in the left column (ie remembers there is calendars) however no data about the calendars is displayed Expected Results: The data for the calendar is usable
Reporter | ||
Comment 2•15 years ago
|
||
Login details provided to Bruno
Assignee | ||
Comment 3•15 years ago
|
||
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.
Attachment #331706 -
Flags: review?(philipp)
Updated•15 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Windows Vista → All
Hardware: PC → All
Updated•15 years ago
|
Flags: blocking-calendar0.9?
Updated•15 years ago
|
Flags: in-testsuite-
Flags: blocking-calendar0.9?
Flags: blocking-calendar0.9+
Updated•15 years ago
|
Flags: in-testsuite-
Updated•15 years ago
|
Attachment #331706 -
Flags: review?(philipp) → review+
Comment 4•15 years ago
|
||
Checked in on HEAD and MOZILLA_1_8_BRANCH -> FIXED
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.9
Reporter | ||
Comment 5•15 years ago
|
||
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!
Status: RESOLVED → VERIFIED
Comment 6•15 years ago
|
||
Don't work for me the build 2008073119 can not get my events the build 2008072919 can get my events with Davical
Comment 7•15 years ago
|
||
on 2008073119 I get the error DAV_NOT_DAV ....
Updated•15 years ago
|
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•15 years ago
|
||
(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?
Comment 9•15 years ago
|
||
(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" ?> <multistatus xmlns="DAV:"> <response> <href>/cal/mdelorme/home/</href> <propstat> <prop> <resourcetype> <collection/> <calendar xmlns="urn:ietf:params:xml:ns:caldav"/> </resourcetype> <HTTP://CALENDARSERVER.ORG/NS/:GETCTAG/> </prop> <status>HTTP/1.1 200 OK</status> </propstat> </response> </multistatus> 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:
Assignee | ||
Comment 10•15 years ago
|
||
[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 <propstat> <prop> <C1:getctag/> </prop> <status>HTTP/1.1 404 Not Found</status> </propstat> ... whereas yours just repeats back the query. What version of DAViCal are you using?
Comment 11•15 years ago
|
||
0.9.1
Assignee | ||
Comment 12•15 years ago
|
||
... 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?
Comment 13•15 years ago
|
||
Unfortunately The upgrade is not planned, so I can't upgrade
Assignee | ||
Comment 14•15 years ago
|
||
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. ->FIXED
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Comment 15•15 years ago
|
||
Bruno, I need a good descriptive relnote-text for this bug (see comment 14). Any suggestions?
Assignee | ||
Comment 16•15 years ago
|
||
(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."
Comment 17•15 years ago
|
||
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...
You need to log in
before you can comment on or make changes to this bug.
Description
•