Response.IsAuthenticated False After 30 Seconds

Discussion in 'ASP.NET / ASP.NET Core' started by nlk10010, Sep 10, 2012.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I recently moved my ASP.NET MVC3 (.NET 4) project from Azure to DiscountASP.NET because of some issues with the former. The app uses SSL FormsAuthentication with a timeout set in web.config to 240 minutes (the Session timeout is 120 minutes).

    The problem I'm having is, when a user leaves a page idle for more than 30-60 seconds and then tries to navigate to a different page they are redirected back to the LogIn URL. Via some testing it seems that, while the session is still intact, Response.IsAuthenticated is being set to false.

    As I mentioned, this problem did NOT occur on Azure or when I run my app locally. Can you suggest a reason why this might be occurring on DiscountASP.NET? Note I'm not "blaming" your site, just trying to figure this out.

    Thanks.
     
  2. dmitri

    dmitri DiscountASP.NET Staff

    This might be due to automatic recycling of the application pool. We host each website in its unique application pool / process. To ensure server stability we recycle the application if any of the following conditions are met:

    1) More than 20 minutes of idle time (no http request in 20 minutes)
    2) The application uses more than 200 MB memory (on IIS 7 hosting)
    3) The application uses more than 70% of CPU resources for more than 3.5 minutes

    Please contact our support department so we can check if your application pool is being recycled due to any of the above conditions.
     
  3. Dmitri:

    Thanks. If you guys can tell me if there's been recycling or not then at least I'll have an idea what's happening.

    I'll submit a ticket.
     
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