Tickets :: Comment on [#12127] utf-16 encoded text files MIME part header broken

* Your Email Address
* Spam protection	Enter the letters below: ._..__..__ ._.. . \| [__][__) \| \|_/ _\|_\| \|\| \_\|_\| \
Comment	>> Those headers should never ever contain NUL bytes >> nor 8-bit data of any kind. That is the key problem. (This bug is not >> about the difficulties detecting the correct charset). > > But this is still potentially an issue similar to what I described. > For example: the browser may send UTF-16 as the charset, but the PHP > conversion methods mishandle it since that is NOT the charset that > the text really is. And/or the fact that PHP string conversion > methods are known to be buggy with UTF16LE (i.e. iconv() on certain > systems). > > At a minimum, I need an example file that triggers this behavior. > Might want to zip/tgz before adding to the ticket to prevent the data > from being munged. >
Attachment
Watch this ticket