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

Kostya Gribov commented on MIME4J-203:
--------------------------------------

Structured fields use RawField.getBody() to extract field body content. This 
method omits only space symbol after field header and colon symbol, but in any 
structured field it should omit any linear-white-space-char sequence. So field 
like "Date:\tFri, 02 Sep 2011 00:00:00 +0300" should be equivalent to "Date: 
Fri, 02 Sep 2011 00:00:00 +0300", but now first variant wouldn't be parsed 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, 0.8
>         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
>
> 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

        

Reply via email to