Summary | iCalendar does not quote/parse parameters correctly |
Queue | Horde Framework Packages |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | jan (at) horde (dot) org, karsten (at) horde (dot) org |
Requester | wrobel (at) horde (dot) org |
Created | 12/05/2008 (6066 days ago) |
Due | |
Updated | 04/05/2009 (5945 days ago) |
Assigned | 12/12/2008 (6059 days ago) |
Resolved | 04/05/2009 (5945 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | 3.3.4 |
Patch | Yes |
http://cvs.horde.org/diff.php/framework/iCalendar/iCalendar.php?rt=horde&r1=1.57.4.74&r2=1.57.4.75&ty=u
http://cvs.horde.org/co.php/framework/iCalendar/tests/quoted-params.phpt?rt=horde&r=1.1.2.1
http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.515.2.523&r2=1.515.2.524&ty=u
State ⇒ Resolved
http://cvs.horde.org/diff.php/framework/iCalendar/iCalendar.php?rt=horde&r1=1.158&r2=1.159&ty=u
http://cvs.horde.org/co.php/framework/iCalendar/tests/quoted-params.phpt?rt=horde&r=1.1
http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.1223&r2=1.1224&ty=u
State ⇒ Assigned
bug #7031but not a duplicate. Parsingcolons is okay (probably as that bug got fixed) but the parsing
problem reported here is about semicolons.
State ⇒ Feedback
bug #7031.Assigned to Karsten Fourmont
State ⇒ Assigned
New Attachment: HK-GW-iCalendar-Quoted_parameters.patch
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ iCalendar does not quote/parse parameters correctly
Type ⇒ Bug
Priority ⇒ 1. Low
contain a ";" when importing data. As per RFC 2445 certain parameter
values need to be quoted. Quoted parameters values are not recognized
by iCalendar.php.
When exporting data the parameters may not contain all possible
characters (e.g. control characters would be invalid). In addition
parameter values that contain a ";", ":", or "," need to be quoted.
Another problem are two byte UTF-8 characters in parameter values: As
far as I can tell RFC 2445 allows these in an unquoted form.
Nevertheless Outlook seems to be unable to deal which unquoted
parameter values when they contain such characters.
See also https://www.intevation.de/roundup/kolab/issue3284
Our suggested solution is to also quote parameter values once there
are two-byte characters in the string.
Suggested patch attached.