james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Commented] (MIME4J-194) ContentTypeFieldImpl (and possibly other parsers in DOM) is unable to handle empty parameters ";;"
Date Mon, 18 Apr 2011 12:10:05 GMT

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

Stefano Bagnara commented on MIME4J-194:
----------------------------------------

I just remembered about isValidField method: most time we parse a field but never check if
the parsing failed (isValidField, getParseException). 

Maybe we should review the code and make sure we don't bring around invalid fields (don't
like this too much because some times it is good to have access to original raw value), or
at least (maybe better) we don't use them as if they were valid. Or maybe ContentTypeFieldImpl
should return text/plain instead of multipart when boundary is not there or when the parsing
fails otherwise (;;).

> ContentTypeFieldImpl (and possibly other parsers in DOM) is unable to handle empty parameters
";;"
> --------------------------------------------------------------------------------------------------
>
>                 Key: MIME4J-194
>                 URL: https://issues.apache.org/jira/browse/MIME4J-194
>             Project: JAMES Mime4j
>          Issue Type: Bug
>          Components: dom
>    Affects Versions: 0.6.1, 0.7
>            Reporter: Stefano Bagnara
>             Fix For: 0.8
>
>         Attachments: contenttypeemptyparameters.msg
>
>
> I guess this is a regression introduced with MIME4J-145. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message