Although I set the contentlength limit to about 4 GB, which is below max
<security> <requestFiltering> <requestLimits maxAllowedContentLength="4294967295"> </requestLimits> </requestFiltering> </security> <httpRuntime targetFramework="4.5" requestValidationMode="2.0" requestPathInvalidCharacters="" maxRequestLength="5024000" executionTimeout="3600" />
I get below the error
HTTP Error 400.0 - Bad Request
ASP.NET detected invalid characters in the URL.
I found a link mentioning the reason for this behavior
https://blogs.msdn.microsoft.com/friis/2013/06/19/uploading-large-file-to-iis-7-5-or-8-using-file-input-element/
If the application runs under the NET 4.5 integrated network, the download will not work above 2G, and the following error will be sent to IIS: "HTTP 400.0 - Invalid ASP.NET request detected invalid characters in the URL.".
When the integrated pipeline is used, we go though the web code (webengine4! MgdGetRequestBasics) that does not support more than 2 GB content length and a System.ArithmeticException exception which subsequently cause an HTTP 400 error. With the classic, we do not use webengine4, but the old model ASPNET_ISAPI and We do not address the above problem.
You need to ask if this is really applicable in IIS 10 and .net framework 4.5.
Is there any parameter that can be set to get around this?
source share