Though I have set the limit of contentlength to around 4GB which is max as below
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="4294967295">
</requestLimits>
</requestFiltering>
</security>
<httpRuntime targetFramework="4.5" requestValidationMode="2.0"
requestPathInvalidCharacters="" maxRequestLength="5024000" executionTimeout="3600" />
I am getting below error
HTTP Error 400.0 - Bad Request
ASP.NET detected invalid characters in the URL.
I found a link which mentions the reason of this behavior
If the application is running under the NET 4.5 Integrated Pipeline, upload will not work above 2G and the following error will be sent by IIS: "HTTP 400.0 – Bad Request ASP.NET detected invalid characters in the URL.".
When the integrated pipeline is used, we go though webengine code (webengine4!MgdGetRequestBasics) which doesn't support more than 2 GB content-length and a System.ArithmeticException exception is raised which subsequently cause the HTTP 400 error. With the classic pipeline, we don't use webengine4 but the old ASPNET_ISAPI model and we don't hit the above issue.
Wanted to ask if this is still valid in IIS 10 and .net framework 4.5.
Is there any setting that can be set to get around this?