ASP.Net MVC 3: Where to handle session loss?

I've started bumping into errors when my session has been lost, or upon rebuilding my project, as my forms authentication cookie still lives on.

In WebForms I'd use the masterpage associated with pages which require login to simply check for the session.

How would I do this in one location in MVC开发者_如何转开发 ? I'd hate having to check for session state in every action in my controllers.

On the other hand I can't just apply a global filter either, since not all Controllers require session state.

Would it perhaps be possible in my layout view ? It's the only thing the pages which require session have in common.

---

One thing you could do is to sub-class the controllers that do need session state. This way you could create a filter on just this base controller. This would allow you to do it all in one place. Plus, as you pointed out, a global filter won't help you here since the logic does not apply to every controller.

---

add it to session start. if a session loss happens it needs to trigger a session start too. you can handle it in there as follows:

protected void Session_Start(object src, EventArgs e)
    {
        if (Context.Session != null)
        {
            if (Context.Session.IsNewSession)
            {
                string sCookieHeader = Request.Headers["Cookie"];
                if ((null != sCookieHeader) && (sCookieHeader.IndexOf("ASP.NET_SessionId") >= 0))
                {
                    // how to simulate it ???   
                    // RedirectToAction(“ActionName”, “ControllerName”,  route values);  
                    Response.Redirect("/Home/TestAction");
                }

            }
        }


    }

---

I agree with what Steve has mentioned, but I suggest to use Global Filters instead of creating a base class for all your controllers. The reason for this is everytime you create a new controller, you should always remember to derive from the base controller or you may experience random behaviours in your application that may take you hours of debugging. This is especially important when you stop development for a while and then get back to it.

Also, another reason is the "Favour composition over inheritance" principle.