Session Early Timeout

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • DZur
    New Member
    • Apr 2008
    • 1

    Session Early Timeout

    Hello,
    I have constructed a Website which requires user login and password.
    There is a Checklogin.asp page which checks for the correct
    username and password as entered in the Registration Form by the user.

    If all goes well for the visitor he is assigned a
    Session("Userna me").
    In addition I placed a Session Timeout Code of 20 minutes:
    <%Session.Timeo ut=20%>
    Also tried this:
    <%Server.Script Timeout = 20%>

    The user giving the correct details enters a member's Main page
    which identifies him by his username:
    Welcome&nbsp;<% =Session("Usern ame")%>
    (which is the important thing ofcourse).

    However when the user tries to link to ANOTHER page after
    staying FOR MORE THAN 6 MINUTES on the member's main page
    his session expires and does not last for the full 20 minutes.
    Must I assign on each and every page the user (well, member) links to, a Session.Timeout Code i.e. <%Session.Timeo ut=20%>
    or was it sufficient to have done so ONCE ONLY on the checklogin page?

    So,
    Linking to other pages from the member's main page 5 minutes and less is ok:
    session does not expire on these OTHER, linked to pages.
    Linking to other pages form the member's main page 6 minutes and up expires the session bringing the user BACK to the login panel.
    I have checked this time and again to be sure of the session timings.
    This may become VERY frustrating for the user should he require MORE TIME on the member's main page.
    Please Help, Thank You Very Very Much.
    Doron.
  • jhardman
    Recognized Expert Specialist
    • Jan 2007
    • 3405

    #2
    There are a couple possible explanations for this to happen:
    1- IIS is not recognizing the different pages to be part of the same web site. This sometimes come up when the site was built with poor-quality wysiwyg editors
    2- IIS is closing the sessions because of an internal setting, or because of heavy traffic
    There could be more, but those are the possibilities that come to mind. It sounds like a question for the IIS forum to me...

    Jared

    Comment

    Working...