james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-118) MIME stream parser handles non-ASCII fields incorrectly
Date Thu, 26 Feb 2009 19:53:02 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677124#action_12677124

Oleg Kalnichevski commented on MIME4J-118:

Looks ok to me. I think ByteSequence and EmptyByteSequence should go into o.a.j.mime4j.util,


> MIME stream parser handles non-ASCII fields incorrectly
> -------------------------------------------------------
>                 Key: MIME4J-118
>                 URL: https://issues.apache.org/jira/browse/MIME4J-118
>             Project: JAMES Mime4j
>          Issue Type: Bug
>            Reporter: Oleg Kalnichevski
>            Assignee: Oleg Kalnichevski
>             Fix For: 0.6
>         Attachments: mime4j-118-bytesequence.patch, mime4j-118-field.patch, mimej4-118.patch
> Presently MIME stream parser handles non-ASCII fields incorrectly. Binary field content
gets converted to its textual representation too early in the parsing process using simple
byte to char cast. The decision about appropriate char encoding should be left up to individual
ContentHandler implementations.
> Oleg

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message