353722 - character escaping issues cause data corruption

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[Dan Mosedale (:dmosedale, :dmose)]

In the event dialog, add text to the beginning of the Description field that has a : in it, such as:

mgmt: foo

Reload the calendar, and look at the Description field again.  It will have a bunch of hex glop inserted into the beginning of the field.  

This definitely happens in the ICS provider, it might well happen in others.

4.3.11 of RFC 2445 defines the various characters that need escaping.  

Marking qawanted, as it would be helpful to understand whether there are other places besides the event dialog that have this problem (eg unifinder, inline text editing widget in the views, etc.).

Comment 1

[Simon Paquet [:sipaq]]

Why is this a blocker? 
Sure, this is ugly, but no really a showstopper for a *0.3* application.

Comment 2

[Stefan Sitter [:ssitter]]

Works for me using Sunbird 0.3a2+ (2006-09-22-01).

I created an event in ics calendar (local disk) and in storage calendar that contained the title and description "mgmt: foo : / \ ? ; ,". 
After doing various restart, reload, export, import actions I don't saw any problems. Title and description were displayed fine.

4.3.11 of RFC 2445 defines:

     text       = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
     ; Folded according to description above

     ESCAPED-CHAR = "\\" / "\;" / "\," / "\N" / "\n")
        ; \\ encodes \, \N or \n encodes newline
        ; \; encodes ;, \, encodes ,

The ics contains:
  SUMMARY:mgmt: foo : / \\ ? \; \,
  DESCRIPTION:mgmt: foo : / \\ ? \; \,

So encoding is done properly.

Maybe a server side issue?

Comment 3

[Matthew (lilmatt) Willis]

This WFM also. I believe it's truly a dupe of bug 268042.

Comment 4

[cmtalbert]

Dmose can you address ssiter's comment above? Are you still seeing this issue with the nightly builds?

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

I'm not seeing this anymore.  I suspect it may well have been a server-side problem that was fixed in recent upgrades to mod_dav_svn or subversion itself.