[Tickets #12161] 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
  Created By         | stuart.carnie at gmail.com
  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             |
------------------------------------------------------------------------------


stuart.carnie at gmail.com (2013-04-05 21: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.

Will provide unit tests and a patch on Github to resolve this issue




stuart.carnie at gmail.com (2013-04-05 21:45) uploaded: sample_msg2.txt

http://bugs.horde.org/h/services/download/?module=whups&actionID=download_file&file=sample_msg2.txt&ticket=12161&fn=%2Fsample_msg2.txt