[
https://issues.apache.org/jira/browse/MIME4J-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614347#action_12614347
]
Stefano Bagnara commented on MIME4J-55:
---------------------------------------
I created MIME4J-57 for the header length issue.
Maybe we can move that issue to a following release (0.5), I don't have a
strong opinion on this.
About me committing to trunk I think I explained why I behaved differently in
the "collaboration & branches" message (it was not intended to become a dev
branch, only a show you that refactoring branch, but something different
happened not under my control and needed review from the team).
I just committed your patch to the streams-refactoring branch.
I didn't commit the EOL conversion of the expected files: they should be
committed in binary form because we want to also fail on different
expected/actual EOLs.
I think there is an issue with mime streams ending with \n that are not
converted to \r\n, but I'll open a JIRA once I'll have verified this.
> Infinite loop on very long boundary (7000 chars)
> ------------------------------------------------
>
> Key: MIME4J-55
> URL: https://issues.apache.org/jira/browse/MIME4J-55
> Project: Mime4j
> Issue Type: Bug
> Reporter: Stefano Bagnara
> Fix For: 0.4
>
> Attachments: mime4j.patch
>
>
> RFC does not mandate parsing of a boundary of that size, but for sure we
> should avoid an infinite loop.
> I committed very-very-long-boundary.msg as a proof.
--
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]
