Develop Reference

413 error on web application even with needed properties in web.config

I have a web application API which is published with IIS.
Clients upload files on my app (via PostMan) which I later process. It has been working fine. Now they tried to upload a large file of 70MB and they get 413 error.
I tried changing parts of web.config:
<system.webServer>
<serverRuntime uploadReadAheadSize="100000" />
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="30000000" />
</requestFiltering>
</security>
</system.webServer>
But I still get the same error. What am I missing?

I also had the same problem a while ago.
The fix is simply to up the size of the UploadReadAheadSize Metabase property.
IIS- uses a new Metabase property called UploadReadAheadSize when passing data to an ISAPI extension.
How To:
The following command instructs you to get the size as follows:
.cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 204800

Large file doesn't upload in ASP.NET

I have a asp.net web form app, i'm trying to upload a large file (13 mb) in a web form with a FileUpload control, when i press the submit button the web browser starts to upload the file. But, when the web browser finish the upload the app crash without reason, and doesn't lauch any exception, and not enter to the click event code (c#) of the submit button. In my web.config i have set the maxAllowedContentLength option and the maxRequestLength option.
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="52428800" />
</requestFiltering>
</security>
<httpRuntime targetFramework="4.5" executionTimeout="900" maxRequestLength="2097151" />
This is only happening in the web server(Windows Server 2012), in my local server this is not happening. In the webserver show a default error (I don't manage the server, so i can't see what custom error is happening)
i don't know why this is happening, because in the web server are apps with file upload options even more bigger.
Thanks for your help.

Modify your web.config by following Stricture, Here I'm using max File request length 13 MB & max Allowed Content Length 1 GB.
Now change Behind the <system.web> in web.config
<httpRuntime targetFramework="4.5" maxRequestLength="13631488" executionTimeout="9000" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="1000" />
And Behind the <system.webServer> in web config write this Code
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="1073741824" />
</requestFiltering>
</security>
Thanks

the problem was a restriction on the server by the admin that doesn't allow upload large files. All the configuration given in this thread are correct.

It looks like you're missing the opening "security" tag in your web.config
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="52428800" />
</requestFiltering>
</security>
</system.webServer>

If your maxAllowedContentLength has a big value, your executionTimeout must be big, too!
It work in local because you don't need a long time to copy file in your hard.
But when you upload your site in server, you need more executionTimeout.

Internal server error 500 on IIS 8

I'm having really a weird problem with my website. It works fine locally, but online it shows iis 8 500 - internal server error.
In the both online and local versions of the site I use the same remote database. The website works online, but it drops when I try to upload a file to the "upload" directory, which is part of the website.
I don't know what the problem is because I can't get any detailed errors. I've added these code pieces in web.config, but still can'tget detailed error descriptions.
<httpErrors errorMode="Detailed" />
<customErrors mode="Off"/>
<compilation debug="true" targetFramework="4.5"/>
<httpErrors errorMode="Detailed" />
I've also set the max file size:
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="4096" />
</requestFiltering>
</security>
and the size of the file I'm trying to upload is only few KBs. I suspect that the user doesn't have write permissions, and I asked the hosting admins to give write permissions (I'm waiting for that right now).
What do you think its the problem? Also, why am I not getting detailed errors?

Write permissions were the reason why I was getting the error.
I gave the folder read/write permissions before, but it looks like they were overridden when the newer project version was published.
(On publish we delete all files on the destination).

issue related to Max File size of Fileupload control

I have deployed my Website on Windows Server 2007. in IIS
I have added asp:FileUpload control
i have set <httpRuntime maxRequestLength="60000"/> under the <system.web> in my Web.Config file
but website doesn't allowed to Save the the file of maxlength as specified in web.config file.
how can i do this?
Thanks..

I think you need to use the following in the web.config file.
<configuration>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="60000" />
</requestFiltering>
</security>
</system.webServer>
</configuration>

In addition to #Maarten answer which is right.
The problem is IIS 7 or greater have default allowed value of maxAllowedContentLength is 30000000 Byte, So if you try to upload a file greater then this limits it will display Request filtering module is configured to deny a request that exceeds the request content length Issue error.
For a demo of this error which this link

IIS7 - Webrequest failing with a 404.13 when the size of the request params exceeds 30mb

I have a simple webmethod
[WebMethod]
public int myWebMethod(string fileName, Byte[] fileContent)
However, whenever I pass a byte array which is larger than 30mb, I get the error:
HTTP Error 404.13 - Not Found
The request filtering module is configured to deny a request that exceeds the request content length.
My web.config is as follows:
<configuration>
<system.web>
<compilation debug="true" targetFramework="4.0"> </compilation>
<authentication mode="Windows" />
<httpRuntime useFullyQualifiedRedirectUrl="true"
maxRequestLength="102400" requestLengthDiskThreshold="102400"
/>
<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID" />
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="104857600"/>
</requestFiltering>
</security>
</system.webServer>
</configuration>
I've searched around, and the most common cause of this problem is the maxAllowedContentLength property being 30mb by default. However, I have set this to be 100mb, as well as the maxRequestLength property for httpRuntime.
I can't find a solution anywhere which isn't setting one of the properties I've already tried above. Is there something I have missed?

You problem may lie in the fact that settings made in the web.config file may be superseded by corresponding settings present in both the applicationhost.config and machine.config files.
If you have access to these, check if the overrideModeDefault property of the corresponding sections are set to Allow, as in the following example:
machine.config
<requestFiltering overrideModeDefault="Allow">
<requestLimits maxAllowedContentLength="104857600"/>
</requestFiltering>
AFAIK there is no way to override these settings if you don't have access to the corresponding configuration file.
You may find more information about system-wide configuration and settings override here, here and here - and a very similar case here.

This is pretty old. But I have the same problem today. To fix this, you need to make the necessary setting changes in web.config, then deploy to the web server. The important part is that you need to re-deploy your application to the web server. By doing so, the IIS settings are updated for you. Depending on how you do your deployment, you may need to delete your web application from the web server first, then deploy again. Updating web.config in place won't fix the problem. Hope this helps others with the same problem.