web analytics

httpruntime executionTimeout vs. SessionState timeout in ASP.NET Web.config


codeling 1595 - 6639
@2022-07-15 09:24:42

The executionTimeout attribute of <httpRuntime> defines the maximum amount of time in seconds that a request is allowed to run before it is automatically terminated by ASP.NET. The default value is 90 seconds. 

This time-out applies only if the debug attribute in the <compilation> element is set to false.

If the time-out expires an exception is raised. You can record the related information in the Application folder of the Event Log. You do this by enabling the application health monitoring in the <healthMonitoring> configuration element.

@2022-07-15 09:30:27

The timeout attribute of <SessionState> Specifies the number of minutes a session can be idle before it is abandoned. The timeout attribute cannot be set to a value that is greater than 525,601 minutes (1 year) for the in-process and state-server modes.

The session timeout configuration setting applies only to ASP.NET pages. Changing the session timeout value does not affect the session time-out for ASP pages. Similarly, changing the session time-out for ASP pages does not affect the session time-out for ASP.NET pages.

The default is 20 minutes.

@2022-07-15 14:06:59

Session timeout is the timeout setting at the session level while httpruntime execution timeout is at he request level. Note that a particular session may have multiple request-response  interactions containd within it and may span multiple aspx pages while request only in the aspx to which you forward your request object.


You must Sign In to comment on this topic.

© 2024 Digcode.com