GNOME Bugzilla – Bug 557281
Evolution does not work with Zimbra CalDAV server.
Last modified: 2009-05-08 06:32:35 UTC
Please describe the problem: Using Evolution with Zimbra 5.0.10 CalDAV server produces an error on creating new appointments. CalDAV is setup using the url "caldav://zimbra.server/dav/user/Calendar". Currently you can view the Calendar, you can move and edit entries. (verified the move on server) however you can not create new appointments and receive the error "Authentication required" My company had opened a case with Zimbra support department and this is the response we had gotten back from them as to why. ----- Forwarded Message ----- It's been a while since I looked at the Evolution client, but when I last tested it Evolution had a major problem with its choice of URL when creating a new appointment. All the other CalDAV clients would use UID of the appointment as the URL to the appointment, which makes appointment retrieval possible for Zimbra. We do issue HTTP redirect on the create request to the URL we can handle, which was working back then but it looks like Evolution doesn't like seeing redirect on the create request any more. Long story short, we can't support Evolution until they start using UID when creating new appointments. Steps to reproduce: 1. Setup Evolution with Zimbra CalDAV. (caldav://zimbra.server/dav/user/Calendar) 2. Authenticate and view Calendar. 3. Create new appointment. Actual results: On creating new appointment you receive the error "Authentication required". Expected results: New appointment should be created and synced with the server. Does this happen every time? yes Other information:
Thanks for the bug report. Is your Evolution version really 2.24.x? The redirections are in since bug #537718, which is included in 2.24.0. I tried to reproduce but I can create appointments on the Zimbra calendar with 2.25.2, which is quite similar to 2.24.2 (it has irrelevant changes to CalDAV backend).
Please feel free to reopen the bug if it doesn't work for you in 2.26.o or later, thanks. *** This bug has been marked as a duplicate of 537718 ***