GNOME Bugzilla – Bug 616543
CalDAV URL gets truncated after a hash character (#)
Last modified: 2011-09-01 08:04:44 UTC
In Ubuntu Daniel Sager reported: When I set up a new CalDAV calendar (in my case the birthday calendar of google contacts), the URL is always truncated after the hash character. This also happens if the # is encoded as %23. I hope I provided you with all the information you need, otherwise just ask for it! Performed Steps --------------- 0) Open Evolution 1) File -> New -> Calendar 2) Type = CalDAV 3) Name = MyGoogleContacts 4) URL = caldav://www.google.com/calendar/dav/%23contacts@group.v.calendar.google.com/events 5) Check "Use SSL" 6) Username = user@googlemail.com 7) Click "OK" 8) Open the properies dialog of the created calendar "MyGoogleContacts" Expected Result --------------- URL = caldav://www.google.com/calendar/dav/%23contacts@group.v.calendar.google.com/events Actual Result ------------- URL = caldav://www.google.com/calendar/dav/ System Info ----------- ~/> lsb_release -rd Description: Ubuntu 9.10 Release: 9.10 ~/> apt-cache policy evolution evolution: Installed: 2.28.1-0ubuntu2 Candidate: 2.28.1-0ubuntu2 Version table: *** 2.28.1-0ubuntu2 0 500 http://de.archive.ubuntu.com karmic-updates/main Packages 100 /var/lib/dpkg/status 2.28.1-0ubuntu1 0 500 http://de.archive.ubuntu.com karmic/main Packages ProblemType: Bug Architecture: i386 Date: Thu Apr 22 11:09:46 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: nvidia Package: evolution 2.28.1-0ubuntu2 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-21.59-generic SourcePackage: evolution Uname: Linux 2.6.31-21-generic i686 Launchpad ref: https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/568304 Thanks!
And if you leave the '#' out entirely? I believe that some web services put a hash character into the URL in order to encourage caching of it, since the # is used to indicate an anchor within the page, so the actual URL really is the bit up to the hash. Of course when you urlencode the hash, that probably should work.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 607812 ***