This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sjt
Recipients barry, mitya57, r.david.murray, sjt
Date 2013-09-21.18:03:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379786618.01.0.40532435822.issue14983@psf.upfronthosting.co.za>
In-reply-to
Content
Seems this hasn't been resolved.  I have to disagree with David's interpretation of RFC 2046.  The definition of a boundary says that it is "terminated" with a CRLF.  It also clarifies that the introducing CRLF is "conceptually part" of the boundary.  Thus each boundary contains both the leading and the trailing CRLF.  There is no exception for the final boundary that I can see.

This implies that when two boundaries abut, they need to be separated by *two* CRLFs, the trailing CRLF on the ending boundary of the inner multipart and the leading CRLF on the next boundary (which might be a separator or the ending boundary) of the containing multipart.
History
Date User Action Args
2013-09-21 18:03:38sjtsetrecipients: + sjt, barry, r.david.murray, mitya57
2013-09-21 18:03:38sjtsetmessageid: <1379786618.01.0.40532435822.issue14983@psf.upfronthosting.co.za>
2013-09-21 18:03:37sjtlinkissue14983 messages
2013-09-21 18:03:37sjtcreate