[
https://issues.apache.org/jira/browse/MIME4J-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020987#comment-13020987
]
Stefano Bagnara commented on MIME4J-194:
----------------------------------------
I suspected that ";;" was not rfc compliant, thank you for checking!
So, probably we should deal with this the same way we deal with
"lenient"/"strict" parsing elsewhere (using Monitor object).
That said I think this behaviour shows another issue with input files having
weird Content-Types: if you parse a message having Content-Type:
multipart/mixed and no boundary parameter it seems that mime4j doesn't
complaint about it while parsing but build a bad object that will fail when
written by the MimeWriter: am I right? If this is right then we probably have
to open a new bug for this. Expected valid behaviours:
1) fail parsing at all
2) ignore the Content-Type header as it is not valid and build a text/plain
message instead.
WDYT?
> 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
