james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (Commented) (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Commented] (MIME4J-203) RawField parsing problem in case of '\t' delimiter
Date Fri, 30 Sep 2011 16:53:45 GMT

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

Oleg Kalnichevski commented on MIME4J-203:


The RawField#getBody used to skip the first blank after the body delimiter, but failed to
do so if the character was a TAB. At the very least the behavior of the method would be consistent:
either always strip the leading white space or strip no content at all.

> RawField parsing problem in case of '\t' delimiter
> --------------------------------------------------
>                 Key: MIME4J-203
>                 URL: https://issues.apache.org/jira/browse/MIME4J-203
>             Project: JAMES Mime4j
>          Issue Type: Bug
>          Components: dom
>    Affects Versions: 0.7
>         Environment: linux 3.0.1, x86_64
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
>            Reporter: Kostya Gribov
>             Fix For: 0.7.1
>         Attachments: patch
> RawField doesn't drop '\t' char between field header and body, so body starts from LWSP-char
that should be ignored by RFC822 (see 3.4.2 in spec) because date field is structured. So
date isn't extracted.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message