Stefano Bagnara wrote:
I opened this issue a week ago:
http://issues.apache.org/jira/browse/MIME4J-54
Given the recent discussions about strict parsing and my view of the
RFC compliance vs real world use case, before spending time in trying
to fix this I would like to know if there is any harm in fixing this.
Please speak now or I'll go on with fixing that issue with no
configurable behaviour: so only boundaries at the beginning of a line
will be parsed.
I would also like to collect opinions about the handling of chars at
the end of the boundary.
From the RFC it's clear we have to deal with padding at the end of the
boundary, but this sentence leave me doubts about what we have to
expect there (from http://www.faqs.org/rfcs/rfc2046.html):
==================================
NOTE TO IMPLEMENTORS: Boundary string comparisons must compare the
boundary value with the beginning of each candidate line. An exact
match of the entire candidate line is not required; it is sufficient
that the boundary appear in its entirety following the CRLF.
=====================================
Do you think this is only about *ending* boundary or *any* boundary?
I've added my response as a comment on the MIME4J-54 issue page.
/Niklas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
