[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         | 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-06 00:01) wrote:

>>>  However, parameter
>>>    values are case-sensitive unless otherwise specified for the specific
>>>    parameter.
>
> What you have quoted is for parameter **values**, not names.  E.g.:
>
> boundary=abc
> is not the same as
> boundary=ABC
>
> Conversely:
>
> BoUnDaRy=abc
> is the same as
> BOUNDARy=abc

Correct, the issue (see my pull request) was that the parameter names  
were not normalized, so a message with a parameter of Boundary (note  
case) was not found.  I created unit tests to demonstrate the issue?