[
https://issues.apache.org/jira/browse/MIME4J-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burrell Donkin reopened MIME4J-90:
-----------------------------------------
Field.parse is a public method. As such, it's not just used by Mime4J. I'm
concerned about the potential impact on users of this method.
Switching from throwing a MimeException to a runtime requires users of that
method to revise their exception handling strategies. Switching to less lenient
parsing only increases this risk.
> Consistent parsing of header field names
> ----------------------------------------
>
> Key: MIME4J-90
> URL: https://issues.apache.org/jira/browse/MIME4J-90
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.5
> Reporter: Markus Wiederkehr
> Priority: Minor
> Fix For: 0.6
>
> Attachments: mime4j-fieldname.patch
>
>
> RFC 822 defines a field as:
> field = field-name ":" [ field-body ] CRLF
> field-name = 1*<any CHAR, excluding CTLs, SPACE, and ":">
> This implies that a field name must consist of at least one character and may
> not contain spaces or tabs; not even trailing ones.
> Currently o.a.j.mime4j.parser.AbstractEntity#parseField accepts empty field
> names while o.a.j.mime4j.field.Field#parse accepts trailing spaces and tabs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
