Handling Response.Redirect in Session end event in global.asax

HI, anilperugu:

Session_End is fired internally by the server, based on an internal timer. Thus, there is no HttpRequest associted when that happens. That is why Response.Redirect or Server.Transferdoes not make sense and will not work.

If i misunderstand you about your question, please feel free to correct me and i will try to help you with more information.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

I need to redirect to some location on session end how can i acheive this at one shot instead of placing code in each page load

I guess that Sesssion end is fired when the session timeout expires.

So possibly it means that closing a browser means that a seesion has ended.

If u want to redirect to any page when the session is ended then

put the following code in the global.asax and please understand

that the event will be fired only when timeout happens.

HI, anilperugu:

HI, anilperugu:

We are marking this issue as "Answered". If you have any new findings or concerns, please feel free to unmark the issue.
Thank you for your understanding!

do i need to place this code in page load of each page.

You can create a base page and put the above codes into the page_load event.

you can check the session in everypage and if the session is dead you can redirect it to

another page. the global.asax file is class class file and it will handle the events of the

sessions and application objects only. we can set some functionalities work along with them.

In the session end event, you can set some application object like

application("active")="true"

then check the application("active") in every page where you can set the redirect method .

With my web apps, I always just use the default session timeout of 5 minutes.

I thought your meta refresh approach was a perfect one until I realized that if the user is on a page that involves a lot of editing, which might normally take a couple of hours, then suddenly after 5 minutes they'll be redirected off of the page to the Login page.  Not acceptable.

In WinForms programming there's a web to monitor keystrokes and mouseclicks which could be used to perpetual move forward the timeout.  Is there not an equivalent way to do that with ASP.Net programming?

Robert

you'd have to use some javascript to update a timer for the client and/or make an ajax call to the server in the background to keep the session open.

It might be better to use Session.IsNewSession

C#

   private void Page_Load(object sender, System.EventArgs e)
    {    
       Response.AddHeader("Refresh",Convert.ToString((Session.Timeout * 60) + 5));     

      if(Session.IsNewSession) 
          Server.Transfer(“Relogin.aspx”);
    }

VB

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load


 Response.AddHeader("Refresh", Convert.ToString((Session.Timeout) * 60 + 5))
        If Session.IsNewSession Then
            Server.Transfer("sessionended.aspx")
        End If

 End Sub