Geek asks and answers

How to prevent a long request in ASP.NET 4.5 from timeout

Do not pay attention to the fact that this is not the best practice, but for a user requirement (there will be only a few users for the application and there will be no simultaneous access) . I need to set a very large execution timeout so the request can even take hours. In the Web.config file, I set the value of the executeTimeout attribute (which determines the number of seconds during which the request can be completed before ASP.NET automatically shuts down) of the httpRuntime element as 3000 (8 hours)

I set the debug attribute on the False compilation element, as it is a prerequisite for setting a large timeout value.

The web application runs on ASP.NET 4.5 and IIS 8.5 / Windows Server 2012.

Even after I set such a high value for the executionTimeout property, the page request expires in 1 hour. How to make the page inaccessible?

Is there a maximum value for the execution of Timeout, for which it cannot be increased? Is there some kind of system parameter value in IIS or Windows Server 2012 forcing the executeTimeout value in web.config to take effect?

+3
source share
1 answer

I don’t know why it does not work for you. But we tried to establish the following values ​​for us.

<httpRuntime maxRequestLength="2147483647" requestValidationMode="2.0" executionTimeout="4800" maxQueryStringLength="2097151" />

together with

<compilation debug="false" targetFramework="4.5">
0
source

More articles:


All Articles