You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Oleg Kalnichevski (JIRA)" <se...@james.apache.org> on 2008/12/07 16:27:44 UTC
[jira] Resolved: (MIME4J-90) Consistent parsing of header field
names
[ https://issues.apache.org/jira/browse/MIME4J-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved MIME4J-90.
-------------------------------------
Resolution: Fixed
Patch checked in
Oleg
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org