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: What about Adobe Flex standard FileReference library? http://stackoverflow.com/questions/13770536/asp-net-web-api-unexpected-end-of-mime-multi-part-stream-when-uploading-from-fl It doesn't add newline characters, so ReadAsMultiPartAsync fails, while working with HTML forms. That's just terrible.
The parser should probably be a little more tolerant to handle this edge case.
Comments: What about Adobe Flex standard FileReference library? http://stackoverflow.com/questions/13770536/asp-net-web-api-unexpected-end-of-mime-multi-part-stream-when-uploading-from-fl It doesn't add newline characters, so ReadAsMultiPartAsync fails, while working with HTML forms. That's just terrible.