Session timeout problem

Discussion in 'ASP.NET / ASP.NET Core' started by cms, Sep 2, 2004.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. cms

    cms

    Hello all. I've got a website here (at http://www.dotnetforum.net) using asp.net. When it comes to session timeout, I haven't touched that in my web.config file or the code within the website. In other words, the session timeout should be 20 minutes which is the default. I just checked the web.config file. Session timeout is set to "20" for 20 minutes. Yet, I've been getting messages from my website saying I'm not logged in (the site has security so you can log in and such) when I have no doubt that I am. I just did some testing by using a stop watch. As best as I can tell, the session timeout appears to be 15 minutes instead of 20 like I want. In fact, it maybe a bit below 15 minutes but it's more than 10 minutes for sure.

    I need the session timeout to be what I set it to. I'm writing a forum applicatoin which I intend to be similar phpBBB if anyone is familiar with that which is used with phpNuke. I noticed the problem when I was typping long messages. I type fairly fast. Yet, sometimes when I type long messages, I hit the submit button and the site tells me I'm not logged in which indicates to me the session has timed out (the userid and some other items are kept in session objects). As I said, I just did informal testing with a stopwatch. The sessions are not lasting 20 minutes like I want but appear to be limited to 15 minutes at the most.

    Is DiscountAsp limiting our sessions in some way? Any ideas what's wrong?


    cms
     
  2. I had a similar problem. Discount ASP do indeed impose limits that effectively overide your session timeout settings. Currently this is set to 10 mins of idle time, i.e. if your site does not receive any requests within 10 mins from the last request, your application is shut down in an effort to conserve system resources. If however your site continues to receive requests your session timeout setting can be effective. Not ideal - I know - but understandable considering several sites are hosted on one machine!

    PS - This is a 'very late' reply... but just incase others have the same problem, I thought it worth while responding!
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page