[
https://issues.apache.org/jira/browse/MIME4J-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614332#action_12614332
]
Stefano Bagnara commented on MIME4J-55:
---------------------------------------
The patch seems ok to me!
Do you think we have to put a limit somewhere to the boundary length we allow
to avoid a very long boundary to make us allocating very big buffers? Maybe
this limit has to be placed during the boundary header decoding? What should
the fallback behaviour be in this case? (maybe parse it as a non multipart?)
About merging code to trunk I'll do this as soon as we solved the
incomprehension about my use of the branch, I'm sure this won't take too much!
Thank you!
> 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]
