Closed
Bug 285779
Opened 19 years ago
Closed 14 years ago
Problems updating with distributed calendar using tomcat webdav
Categories
(Calendar :: Provider: ICS/WebDAV, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: sk, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.54 [en] Build Identifier: The 0.2 Sunbird will not update the remote calendar unless I post something to it. I use the webdav which is enclosed in Tomcat 5.5.x which does not support versioning. Does sunbird only support webdav solutions that provides versioning? Perhaps it should check file size, diff. or other indicators for checking for a new version?!?! This is the only reason for this problem that I can think of, however I might be mistaken. Reproducible: Always Steps to Reproduce: 1. Add something to the calendar with one client that posts it to the Tomcat 5. 5.X Webdav. 2. Tries to update that with another client which doesn't do it. 3. Add something with the other clint which is posted to the webdav, then the changes made with the first client appeares in the second client's calendar. Expected Results: Updated the calender when "asked" to do so.
Updated•19 years ago
|
QA Contact: gurganbl → general
Comment 1•18 years ago
|
||
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
Updated•18 years ago
|
Component: General → Provider: ICS/Webdav
QA Contact: general → ics-provider
Comment 2•16 years ago
|
||
Not quite sure I understand. Does this mean there is a problem with tomcat 5.x servers, which doesn't appear with other servers? Or is it about refreshing the calendar to get the updated version after a certain point in time?
I just tested with the Tomcat 5.5 server and that particular webdav application. The issue is with refreshing the calendar. It doesn't refresh. However I don't know if it's still the case as I haven't tried it since I posted this bug.
Comment 4•14 years ago
|
||
No further response, please reopen when you have tested.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•