Ask a Question related to ASP.NET Security, Design and Development.

  1. #1

    Default Web.config timeout

    The user has indicated that the application seems to be kicking her out, even
    though she is sure that she is submitting a form faster than every 30
    minutes. I thought that I had set the Web.Config on the ASP.NET application
    to time out after 30 minutes of inactivity, but maybe I don't have something
    set up correctly. Here's the basis of my Web.Config (stripped down without
    comments):

    <?xml version="1.0" encoding="UTF-8" ?>
    <configuration>
    <appSettings>
    <add key="ConnectionString" value="User ID=userid;Initial
    Catalog=dbname;Data Source=servername.net;password=userpassword" />
    </appSettings>

    <location path="ForgotPswd.aspx"><system.web><authorization> <allow
    users="*" /></authorization></system.web></location>

    <system.web>
    <sessionState mode="InProc"
    timeout="30" />
    <compilation debug="true"/>
    <customErrors mode="Off"/>

    <authentication mode="Forms">

    <forms name=".ASPXAUTH"
    loginUrl="login.aspx" />
    </authentication>

    <authorization>
    <deny users="?" />
    </authorization>
    </system.web>
    </configuration>

    Additionally, I have this in the Page_Load of the web page:
    Response.AddHeader("Pragma", "no-cache")
    Response.Expires = -1
    Response.Expiresabsolute = Now().Subtract(New TimeSpan(1, 0, 0, 0))
    Response.CacheControl = "no-cache"

    Do you see any reason why it would expire unless they truly had 30 minutes
    of no activity submitted to the server? Is there anything wrong here?
    Thanks.

    LisaConsult Guest

  2. Similar Questions and Discussions

    1. #40750 [NEW]: fsockopen timeout parameter overwrites timeout for reading
      From: andreas dot rieber at 2e-systems dot com Operating system: OpenSuse PHP version: 5.2.1 PHP Bug Type: Network related...
    2. WebService ignoring timeout properties? (Server was unable to process request. --> Timeout exired)
      Hi! I have a webservice serving the latest orders from a webshop. The customer uses a forms app client to fetch these orders and push them into...
    3. Can I set the Web.config <forms> element timeout value progmatically?
      I am using Windows Forms authentication in my ASP.NET app. In Web.Config, I would like to set the timeout value in the <forms> element in C# code...
    4. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
      Gary Why not just change the connection timeout property? Your doing an update statement, which could take various amounts of time depending on...
    5. Session timeout in .config file
      I have an ASP.Net application running one level above the root web server. The root web server is configured for a 60 min session timeout. If I...
  3. #2

    Default RE: Web.config timeout

    The <forms> element also has an attribute "Timeout", you may set it to a
    large to see if it will help. Or you may consider use Persistent cookies
    cookie for the form authentication.

    Hope this help,

    Luke

    [MSFT] Guest

  4. #3

    Default RE: Web.config timeout

    But, please help me to understand, what would be kicking the user out of the
    session if they were sending information to the server and everything below
    looks fine? What would cause the session to be lost. The user assures me
    that when this occurs it's about 1-2 minutes per submission, not 30 minutes.
    We currently don't want to go the cookie route.

    "[MSFT]" wrote:
    > The <forms> element also has an attribute "Timeout", you may set it to a
    > large to see if it will help. Or you may consider use Persistent cookies
    > cookie for the form authentication.
    >
    > Hope this help,
    >
    > Luke
    >
    >
    LisaConsult Guest

  5. #4

    Default RE: Web.config timeout

    Hello,

    Since you use Forms authentication, a cookie will be sent to client,
    indicating the user has been authenticated. If this is timeout (not the
    session), the user will be redirect to the login in page if they request to
    server.

    Luke

    [MSFT] Guest

  6. #5

    Default RE: Web.config timeout

    I just found out that this web app was moved from a Win2K server to a Win2003
    server last week. This is when the problem began occuring, is there a
    difference between the OSs which would cause this? Thanks.

    "[MSFT]" wrote:
    > Hello,
    >
    > Since you use Forms authentication, a cookie will be sent to client,
    > indicating the user has been authenticated. If this is timeout (not the
    > session), the user will be redirect to the login in page if they request to
    > server.
    >
    > Luke
    >
    >
    LisaConsult Guest

  7. #6

    Default RE: Web.config timeout

    Generally speaking, Windows 2000 works with IIS 5.0 and Windows server 2003
    with IIS 6.0 and .NET framework 1.1. There are many differences between
    them. Besides, the two computers may have different machine.config and
    security settings. I suggest you may first try to set the timeout value for
    forms authentication, and see if this can fix the problem. If not, we can
    go to see other issues related.

    Luke

    [MSFT] Guest

  8. #7

    Default RE: Web.config timeout

    I apologize for the lack of mentioning it. I did place a Timeout in the
    Web.Config like this:
    <authentication mode="Forms">
    <forms name=".ASPXAUTH"
    loginUrl="PAE/login.aspx" />
    </authentication>

    The user is still getting kicked out of the system. The odd thing is that
    it's sporadic. She can get kicked out 5 times in 7 hours or 1 time in 5
    minutes with no real consistency about it. It is not always in the same
    screen either. Thanks for your continued assistance.

    "[MSFT]" wrote:
    > Generally speaking, Windows 2000 works with IIS 5.0 and Windows server 2003
    > with IIS 6.0 and .NET framework 1.1. There are many differences between
    > them. Besides, the two computers may have different machine.config and
    > security settings. I suggest you may first try to set the timeout value for
    > forms authentication, and see if this can fix the problem. If not, we can
    > go to see other issues related.
    >
    > Luke
    >
    >
    LisaConsult Guest

  9. #8

    Default RE: Web.config timeout

    What is the value you set for form authenttication?

    <authentication mode="Forms">
    <forms name=".ASPXAUTH"
    loginUrl="PAE/login.aspx" />
    </authentication>

    And, is the only user who encounter the problem? If so, did she have any
    proxy/firewall between her and the server? Any, any antivirus software
    installed?

    Luke



    [MSFT] Guest

  10. #9

    Default RE: Web.config timeout

    <authentication mode="Forms">
    <forms name=".ASPXAUTH"
    loginUrl="PAE/login.aspx"
    timeout="20"/>
    </authentication>

    Currently there is only one consistent user within the organization.
    Because the system is in Beta, there are currently no other users. The
    application is hosted by an outside host provider. They are going through a
    firewall and they do have norton antivirus software installed.

    "[MSFT]" wrote:
    > What is the value you set for form authenttication?
    >
    > <authentication mode="Forms">
    > <forms name=".ASPXAUTH"
    > loginUrl="PAE/login.aspx" />
    > </authentication>
    >
    > And, is the only user who encounter the problem? If so, did she have any
    > proxy/firewall between her and the server? Any, any antivirus software
    > installed?
    >
    > Luke
    >
    >
    >
    >
    LisaConsult Guest

  11. #10

    Default RE: Web.config timeout

    Since the problem was sporadic, it looks to me that it is a configration
    issue. The timeout settings are fixed and won't be random. Based on my
    experience, it may be a problem related to the outside host provider. I
    suggest you may contact them, and ask if they have found such an issue fore
    other clients. Especially, for session and cookie.

    Luke

    [MSFT] Guest

  12. #11

    Default RE: Web.config timeout

    Hello,

    Any progress? Did the outside host provider give some suggstions on this
    issue?

    Luke

    [MSFT] Guest

  13. #12

    Default Re: Web.config timeout

    By the look of it, this web.config must be a config file in a sub
    folder. I presume so because of the <location path=> attribute. If this
    is so, change the root web.config file.


    with regards,


    J.V.Ravichandran
    - [url]http://www.geocities.com/[/url]
    jvravichandran
    - [url]http://www.411asp.net/func/search?[/url]
    qry=Ravichandran+J.V.&cob=aspnetpro
    - [url]http://www.southasianoutlook.com[/url]
    - [url]http://www.MSDNAA.Net[/url]
    - [url]http://www.csharphelp.com[/url]
    - [url]http://www.poetry.com/Publications/[/url]
    display.asp?ID=P3966388&BN=999&PN=2
    - Or, just search on "J.V.Ravichandran"
    at [url]http://www.Google.com[/url]

    *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
    Don't just participate in USENET...get rewarded for it!
    Ravichandran J.V. Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139