Not sure if the spec requires a CR/LF combination at the end of a multipart stream, but there are many file uploaders out there that do not append a CRLF at the end. The MimeMultipartBodyPartParser fails under this scenario.
The parser should probably be a little more tolerant to handle this edge case.
Comments: While it is technically allowed not to have the CRLF as part of the boundary all the MIME multipart generators we have tries (notably all the major browsers) do generate it. Adding support for this has a surprising effect on the complexity of the parser and so we prefer not to do it at this time.
The parser should probably be a little more tolerant to handle this edge case.
Comments: While it is technically allowed not to have the CRLF as part of the boundary all the MIME multipart generators we have tries (notably all the major browsers) do generate it. Adding support for this has a surprising effect on the complexity of the parser and so we prefer not to do it at this time.