ansaurus

Question

Answer 1

A:

What you could do is to add a invisible iframe to your page:

<iframe src="keepalive.aspx" style="width:0px;height:0px"></iframe>

And keepalive.aspx contains the following:

<%@ Page Language="C#" Inherits="Keepalive" EnableSessionState="True"%>
<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" >
<html>
  <head>
   <META http-equiv="refresh" content="60"/>
  </head>
  <body></body>
</html>

Every 60 seconds keepalive.aspx refreshes itself causing the session to stay alive. You can set the timeout of the session to for instance 2 minutes. This way the session will be cleaned up very soon after the user has left your page.

Corne 2009-11-26 08:19:14

Answer 2

A:

It's a bad idea to have pernament sessions on you site but you can acomplish this by giving large values for session time out in web.config

<sessionState  timeout="6000"/>

MichaelT 2009-11-26 08:42:02

Answer 3

+1 A:

I'm not sure where your problem lies, but as an alternative consider using a javascript solution client side to prompt the user to renew their session prior to expiration. If the user fails to affirmatively agree to session renewal, then redirect to the Logout page to terminate the session without simply letting it expire. Typically your Logout page will redirect back to the Login page so the user, when they return to their computer, will be prompted to Login. If the user does click the OK (I want to renew my session) button in your renewal dialog, then use a request to a Keepalive page, as @Come suggests, though I would do it with AJAX instead of an iframe.

You can look at some sample code that does this in an ASP.NET MVC context on my blog.

tvanfosson 2009-11-26 14:26:27

Answer 4

A:

This article might help you code a solution to your problems:

http://aspalliance.com/520%5FDetecting%5FASPNET%5FSession%5FTimeouts

code4life 2009-11-26 16:33:29

Answer 5

+1 A:

I have solved this in my master page's Page_Load.

Each time the Page_Load fires it checks to see that a specific Session value exists (which should be there if a user is signed in properly). If not I redirect to the sign in page.

Eg:

// Assuming your using master pages (if not you could have this in a base page that all
// your pages inherit from.
protected void Page_Load(object sender, EventArgs e)
{
    if (Session["SomeKey"] == null)
    {
        // Session has expired or person has not signed in so redirect.
        FormsAuthentication.SignOut();
        Session.Abandon();
        Response.Redirect("signin.aspx", true);
    }

    // If all is good continue and do whatever you normally do.
}

In your example the session variables might not exist due to the session expiring so your getting null back from all your fetched session keys. You should be validating that they are not null and if so reacting appropriately to the values being null.

Kelsey 2009-11-26 16:42:16

ansaurus

tags:

views:

answers:

session expiring and giving error page

related questions