[
https://issues.apache.org/jira/browse/MIME4J-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated MIME4J-194:
-------------------------------------
Component/s: (was: parser (core))
dom
Affects Version/s: 0.6.1
Fix Version/s: (was: 0.7)
0.8
Summary: ContentTypeFieldImpl (and possibly other parsers in DOM)
is unable to handle empty parameters ";;" (was: There is a regression when
content type include empty parameters ";;")
Yes, ContentTypeFieldImpl appears to be the culprit. I managed to reproduce the
problem locally with a trivial test case similar to that I submitted for
RawFieldParser. Apparently the field value is not compatible with the grammar
defined in ContentTypeParser.jj and also likely to violate the strict
interpretation of RFC 2045.
I am completely helpless with JavaCC and will not be able to fix the problem
for 0.7. I'll have to re-target it to 0.8 unless someone else volunteers.
Oleg
> 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
