[Bug 31170] New: Chan.I.Messages: decide if the values of "content-type" body part keys must be normalized

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=31170

           Summary: Chan.I.Messages: decide if the values of
                    "content-type" body part keys must be normalized
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: mikhail.zabaluev at nokia.com
         QAContact: telepathy-bugs at lists.freedesktop.org


The current specification of Channel.Interface.Messages does not require that
the value of a body part key "content-type" must be normalized in some way.
Some existing code, including the proposed implementation in bug #29377, uses
case-sensitive string comparisons for the value, e.g. expecting it to be
strictly lowercased "text/plain". MIME and derived specifications allow content
types to be case-insensitive, so mixed-case values can be received from
protocols.
The specification should be clear on what kind strictness is expected for
messages passed by the client and message data signalled by the connection
manager.

I'd say we should treat client-supplied values liberally (and thus change the
comparisons to be case-insensitive in the CMs), but lowercase the values
reported by CMs (as the current implementations happen to do).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.