Ned Freed <NED(_at_)innosoft(_dot_)com> writes:
NOTE TO IMPLEMENTORS: Boundary string comparisons must take into
account the full contents of the candidate line containing a
possible boundary string. Specifically, the entire string following
the CRLF and two dashes up to either the final two dashes or the
final CRLF must be compared with the boundary parameter. An exact
match is required; a substring match is not sufficient.
NO, NO, NO, NO, NO!
Implementations are required to ignore trailing whitespace on boundary
lines. If implementations can't do a match on the "<CRLF>--outer",
then they have to be able to do an *arbitrary* amount of lookahead, to
make sure there isn't a non-whitespace octet between the 35 megabytes
of spaces/tabs and the following CRLF.
We had a perfectly good grammar worked out on the list around the 25th of
October. Can't we just stick with that?
--
_.John G. Myers Internet: jgm+(_at_)CMU(_dot_)EDU
LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up