hey all. i have a Cosmo bug (<https://bugzilla.osafoundation.org/show_bug.cgi?id=7951>) that revolves around a CS-generated iCalendar object containing an ATTACHMENT property: ATTACHMENT:http://www.example.com/test.jpg RFC 2445 doesn't define an ATTACHMENT property, only ATTACH. does CS actually generate this, or was it hand-crafted somehow? to the best of my knowledge it came to our attention during a CalConnect interop session.
Hi Brian, --On June 21, 2007 10:44:36 AM -0700 Brian Moseley <bcm@osafoundation.org> wrote:
hey all. i have a Cosmo bug (<https://bugzilla.osafoundation.org/show_bug.cgi?id=7951>) that revolves around a CS-generated iCalendar object containing an ATTACHMENT property:
ATTACHMENT:http://www.example.com/test.jpg
RFC 2445 doesn't define an ATTACHMENT property, only ATTACH.
does CS actually generate this, or was it hand-crafted somehow? to the best of my knowledge it came to our attention during a CalConnect interop session.
Did this come from a CalDAVTester test run? I believe there are some erroneous hand-crafted iCalendar components in there that use ATTACHMENT instead of ATTACH. I need to fix that... -- Cyrus Daboo
On 6/21/07, Cyrus Daboo <cdaboo@apple.com> wrote:
Did this come from a CalDAVTester test run? I believe there are some erroneous hand-crafted iCalendar components in there that use ATTACHMENT instead of ATTACH. I need to fix that...
it's possible... the first i saw of it was when Mikeal Roger logged the Cosmo bug about ATTACHMENT causing an error. if it's not something legitimate that i have just never seen, then i can close out that bug. thanks :D
participants (2)
-
Brian Moseley
-
Cyrus Daboo