ASP/C#.NET (web forms, not MVC)After a good bit of research, I have come to the understanding that, in general, when using Response.Redirect(), it is better to pass FALSE for the second parameter, to avoid System.Threading.ThreadAbortException. (http://blogs.msdn.com/b/tmarq/archive/2009/06/25/correct-use-of-system-web-httpresponse-redirect.aspx)My question is, "Is there a recommended way (pattern) for managing (namely skipping) processing in page events that fire after the redirect, when false is passed for the second parameter?" This is mostly a problem for me when I am checking for and redirecting on an expired session in Page_Load(). It seems very tedious to have to perhaps set a "Session OK" flag in Page_Load() and then check that flag at the top of every event. I haven't had to worry about this in the past because I always passed TRUE for the second parameter, not knowing any better.Below is some code showing what I don't want to have to do (check _SessionOK for each event). Perhaps what I'm looking for is a better Session Expiration Processing pattern. Any suggestions on how to improve this processing, would be greatly appreciated.\[code\]private bool _SessionOK = false; protected void Page_Load(object sender, EventArgs e){ _SessionOK = (Session["key"] != null); if (!SessionOK) { Response.Redirect("SessionExpired.aspx", false); } }protected void Button1_Click(object sender, EventArgs e){ if (_SessionOK) { // do Button1_Click() stuff... }}protected void Button2_Click(object sender, EventArgs e){ if (_SessionOK) { // do Button2_Click() stuff... }}\[/code\]