＆QUOT; MIME多流。 MIME多信息是不完整的＆QUOT;错误上的WebAPI上传 [英] "MIME multipart stream. MIME multipart message is not complete" error on webapi upload

问题描述

我上传到的WebAPI控制器时，只收到某些文件的错误。

I receive only on certain files an error when uploading to a webapi controller.

该错误是MIME多流。MIME多信息是不完整的

The error is "MIME multipart stream. MIME multipart message is not complete"

这似乎错误是与某种不好终止POST数据，但是当我检查从萤火一切浏览器发送的参数似乎确定。

It seems the error is linked to some kind of not well terminated POST data but as I inspect the parameters sent from the browser with firebug everything seems ok.

<一个href=\"http://forums.asp.net/t/1777847.aspx/1?MVC4%20Beta%20Web%20API%20and%20multipart%20form%20data\"相对=nofollow>这个帖子提出一个解决办法，不为我工作。我也看了一下这

This post propose a workaround that doesn't work for me. I have looked also at this

我利用MultipartFormDataStreamProvider反序列化。

I am utilizing the MultipartFormDataStreamProvider for deserialization.

下面一个链接两个类似的PDF文件，一个工作，一个没有。
我还包括另一样本HTML5的WebAPI上传应用程序从<一来压缩href=\"http://www.strathweb.com/2012/04/html5-drag-and-drop-asynchronous-multi-file-upload-with-asp-net-webapi/\"相对=nofollow> strathweb.com 。
该应用程序将一个文档工作，而不是其他。

Here a link to two similar pdf documents, one working and one not. I included also the zip of another sample html5 webapi upload application coming from strathweb.com. The application will work with one doc and not the other.

推荐答案

根据这个讨论，应该固定的ASP.NET Web API的下降：

According to this discussion, it should be fixed in the next drop of ASP.NET Web API:

我们已经看过这个，虽然它使用的测试位瑞普我们已经证实，该问题已在最新的位得到解决。你可以尝试一下最新的每晚构建（见<一href=\"http://blogs.msdn.com/b/henrikn/archive/2012/04/29/using-nightly-nuget-packages-with-asp-net-web-stack.aspx\"相对=nofollow>这里指令）或等待我们的下降。

We have looked into this and while it does repro using the beta bits we have confirmed that the issue has been resolved in the latest bits. You can either try out the latest nightly build (see instructions here) or wait for our next drop.

这篇关于＆QUOT; MIME多流。 MIME多信息是不完整的＆QUOT;错误上的WebAPI上传的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！