They are not the same. The IIS session timeout is for clasic ASP pages. The web.config one is for asp.net.
More Related Contents:
- I just discovered why all ASP.Net websites are slow, and I am trying to work out what to do about it
- Losing Session State
- asp.net – session – multiple browser tabs – different sessions?
- How can I share a session across multiple subdomains in ASP.NET?
- Session lock causes ASP.Net websites to be slow
- System.Diagnostics.Process.Start not work from an IIS
- What should I do if the current ASP.NET session is null?
- ASP.NET: Session.SessionID changes between requests
- Access-control-allow-origin with multiple domains
- HTTP Error 503, the service is unavailable
- IIS7 Cache-Control
- ASP.NET Web API OperationCanceledException when browser cancels the request
- ASP.NET Core with IIS – HTTP Verb Not Allowed
- HTTP Error 500.22 – Internal Server Error (An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.)
- Caching specific Javascript and CSS files
- What is limiting the # of simultaneous connections my ASP.NET application can make to a web service?
- In ASP.NET, when should I use Session.Clear() rather than Session.Abandon()?
- NuGet: ‘X’ already has a dependency defined for ‘Y’
- ASP.net session request queuing
- ASP.NET MVC – Session is null
- IIS7 – The request filtering module is configured to deny a request that exceeds the request content length
- ASP.NET 5 project hosting on IIS
- Script not served by static file handler on IIS7.5
- What does ‘IISReset’ do?
- Asp.Net Session is null in ashx file
- SignalR and Browser Connection limit
- ASP.NET Why are sessions timing out, sessionstate timeout set
- What is an IIS application pool?
- Maximum default POST request size of IIS 7 – how to increase 64kB/65kB limit?
- 404 Redirecting for non aspx pages