Session Timeout, not working

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Scott

    Session Timeout, not working

    I have set the session timeout something greater then 20 minutes in
    the web.config(120 minutes for testing) after 20 minutes to 30 minutes
    click a button and am redirected back to the login. My Session is
    reporting 120 minutes I know this becuase I display on a debug page.
    below are the 2 areas in the web.config that I set anybody tell me
    whats wrong or what is missing.

    <sessionState mode="InProc" regenerateExpir edSessionId="fa lse"
    timeout="120">
    </sessionState>

    <forms name=".GSNAUTH" loginUrl="Login .aspx" path="/"
    protection="Enc ryption" timeout="120" slidingExpirati on="true"/>

    When previeing on the page I see the top 1 becuase I have been able
    to adjust it down to 60 minutes or 35 minutes whatever.

    When I display on the debug page I show
    lblSessionTimeo ut.text = Session.Timeout ;

    NOt sure what I am missing.
  • Anthony Jones

    #2
    Re: Session Timeout, not working

    "Scott" <sremiger@groce ryshopping.netw rote in message
    news:47b0bb72-a003-4f59-9e19-fb5cbe61e720@o7 7g2000hsf.googl egroups.com...
    I have set the session timeout something greater then 20 minutes in
    the web.config(120 minutes for testing) after 20 minutes to 30 minutes
    click a button and am redirected back to the login. My Session is
    reporting 120 minutes I know this becuase I display on a debug page.
    below are the 2 areas in the web.config that I set anybody tell me
    whats wrong or what is missing.
    >
    <sessionState mode="InProc" regenerateExpir edSessionId="fa lse"
    timeout="120">
    </sessionState>
    >
    <forms name=".GSNAUTH" loginUrl="Login .aspx" path="/"
    protection="Enc ryption" timeout="120" slidingExpirati on="true"/>
    >
    When previeing on the page I see the top 1 becuase I have been able
    to adjust it down to 60 minutes or 35 minutes whatever.
    >
    When I display on the debug page I show
    lblSessionTimeo ut.text = Session.Timeout ;
    >
    NOt sure what I am missing.

    Unless you have other clients creating activity on the site your Application
    Pool is probably timing out. When a pool has seen absolutely no activity
    whatsoever it can shutdown. Check the settings on the pool to which your
    application belongs.


    --
    Anthony Jones - MVP ASP/ASP.NET


    Comment

    • =?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=

      #3
      RE: Session Timeout, not working

      Session expiration and forms authentication timeouts are two separate and
      distinct things. Being redirected to a login page is a forms authentication
      timeout issue, unless somehow you are also using session to do this.
      Your ASP.NET application can recycle for any number of reasons, and when it
      does, all inProc Sessions go bye-bye.
      -- Peter
      Site: http://www.eggheadcafe.com
      UnBlog: htp://petesbloggerama .blogspot.com
      Short Urls & more: http://ittyurl.net


      "Scott" wrote:
      I have set the session timeout something greater then 20 minutes in
      the web.config(120 minutes for testing) after 20 minutes to 30 minutes
      click a button and am redirected back to the login. My Session is
      reporting 120 minutes I know this becuase I display on a debug page.
      below are the 2 areas in the web.config that I set anybody tell me
      whats wrong or what is missing.
      >
      <sessionState mode="InProc" regenerateExpir edSessionId="fa lse"
      timeout="120">
      </sessionState>
      >
      <forms name=".GSNAUTH" loginUrl="Login .aspx" path="/"
      protection="Enc ryption" timeout="120" slidingExpirati on="true"/>
      >
      When previeing on the page I see the top 1 becuase I have been able
      to adjust it down to 60 minutes or 35 minutes whatever.
      >
      When I display on the debug page I show
      lblSessionTimeo ut.text = Session.Timeout ;
      >
      NOt sure what I am missing.
      >

      Comment

      Working...