Maximum http request size for asp web.api with jso

问题:

I have web api project.

I need to post there json data with file as encoded base64 string (up to 200 mb).

If i send data up to about 10 mb, then next method normally get properly filled model ImportMultipleFileModel.

[HttpPost]
    public async Task<HttpResponseMessage> ImportMultipleFiles(ImportMultipleFileModel importMultipleFileModel)
    { 
        var response = ImportFiles(importFileModel);
        return response;
    }

If i send more, then model is null.

Why?

So i change method signature to:

    [HttpPost]
        public async Task<HttpResponseMessage> ImportMultipleFiles()
        {
            ImportMultipleFileModel importMultipleFileModel = null;
            var requestData = await Request.Content.ReadAsStringAsync();
            try
            {
                JsonConvert.
                importMultipleFileModel = JsonConvert.DeserializeObject<ImportMultipleFileModel>(requestData);
            }catch(Exception e)
            { }
}

And for encoded 30 mb file i normally get requestData as json string. For 60 mb i get empty string. Why?

Next i change method to

    [HttpPost]
        public async Task<HttpResponseMessage> ImportMultipleFiles()
        {
            ImportMultipleFileModel importMultipleFileModel = null;
            var requestData = Request.Content.ReadAsStringAsync().Result;
            try
            {
                importMultipleFileModel = JsonConvert.DeserializeObject<ImportMultipleFileModel>(requestData);
            }catch(Exception e)
            { }
}

And deserialization failed because of OutOfMemoryException.

Why?

UPD: maxRequestLength, maxAllowedContentLength set to 2147483647

回答1:

Try setting the maxRequestLength.

<httpRuntime targetFramework="4.5" maxRequestLength="65536" />

Or maxAllowedContentLength (I always get confused which one's which).

<security>
  <requestFiltering>
    <requestLimits maxAllowedContentLength="52428800" />
  </requestFiltering>
</security>

Also, I would reconsider posting data this way. Read this article form MSDN, it's mainly for WCF, but I think the content is mostly valid.

The strategy to deal with large payloads is streaming.

Side note for your last example; you should not (or perhaps rarely) use .Result when you can use await. Stephen Cleary wrote a good answer on that here.