Hide Forgot
Description of problem: SSIA, remote CalDav calendars are inaccessible beause of the bug. Version-Release number of selected component (if applicable): evolution-data-server-2.28.3-15.el6.x86_64 How reproducible: always Steps to Reproduce: 1. set up Evolution to use remote CalDav calendar with space in URI 2. verify that uri in <source> element in /apps/evolution/calendar/sources contains ' ' or '%20' 3. kill all evolution processes, run 'CALDAV_DEBUG=all /usr/libexec/evolution-data-server-2.28' 4. run evolution Actual results: path passed to server has space/'%20' replaced to '%2520' string Expected results: URI is passed with '%20' Additional info:
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Created attachment 520354 [details] eds patch for evolution-data-server CalDAV calendar backend; This helped me. I have written that space as a space (decoded), in calendar Preferences URI and it is properly used in CalDAV backend, with this patch.
Patch in comment 3 fixed the issue for me.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. It has been proposed for the next release. If you would like it considered as an exception in the current release, please ask your support representative.
Hmm, this is dupe of bug #692658, or vice versa.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0410.html