[Tickets #12161] Re: Unable to parse certain multi-part messages

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12161
------------------------------------------------------------------------------
  Ticket             | 12161
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Unable to parse certain multi-part messages
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-04-05 17:45) wrote:

> The Boundary parameter of the Content-Type header has an uppercase  
> B, however per section 2 of RFC 2045  
> (http://tools.ietf.org/html/rfc2045#section-2):
>
>    All numeric and octet values are given in decimal notation in this
>    set of documents. All media type values, subtype values, and
>    parameter names as defined are case-insensitive.  However, parameter
>    values are case-sensitive unless otherwise specified for the specific
>    parameter.

1) The message sample that your provided was from H4 (with a 2009)  
date, which is old unsupported software.
2) We don't set the phrase 'Boundary' anywhere in the current code.
3) You are incorrect in your reading of the RFC.  Content-Type  
parameter names are NOT case-sensitive.  RFC 2045 [5.1]:

"The type, subtype, and **parameter names** are not case sensitive."  
(emphasis added).

IIRC, Pine would always send its Content-Type parameter names in  
uppercase, for example.