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

* Your Email Address
* Spam protection	Enter the letters below: __ . .. ..__ . . / `\|\ \|\ /[__)\| \| \__.\| \\| \/ \| \|__\|
Comment	>> 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.
Attachment
Watch this ticket