One of my co-workers here pointed out RFC-1521 which has an example using two
boundaries "unique-boundary-1" and "unique-boundary-2".
Doug Strauss
Microsoft System Testing
----------
From: Steve Dorner
Sent: Thursday, February 09, 1995 8:02AM
To: ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu
Subject: MIME boundary question
Consider the following fragment:
multipart/mixed; boundary="outer"
--outer
multipart/mixed; boundary="outer-inner"
--outer-inner
stuff
--outer-inner--
--outer--
I have a vendor claiming that this is illegal because the "outer" appears
in the boundary "outer-inner", and thus violates the need for the
boundaries to be unique. Their claim is in fact that "outer" must appear
NOWHERE in the body--not merely that "--outer<CRLF>" must not appear in the
body.
I think this is absolutely preposterous. I think that the uniqueness
requirement means that the string "--outer<CRLF>" must not appear as body
contents, but that "--outer-inner<CRLF>" is perfectly OK (so far as the
outer multipart goes), and that the fragment above is therefore perfectly
ok.
What say you all? Have I misread the RFC? Has the other vendor? Does the
RFC need to be clarified?
--
Steve Dorner, Qualcomm Incorporated. "Oog make mission statement."