I have set my formsauthentication cookie to expire in 180 minutes. I set the IIS timeout to 180 mins also ..actually (180 * 60 ) seconds ..
I also set the timeout in my web.config SessionState tag to 180 minutes.
Users experience a slow down every now and then to my app. Of course there could be a number of reasons but I think 3 hours is far too long to set for idle time. What do you think?
My server has 4gig memory and 2 websites setup on it with one website running terminal services and the other running ASP.Net.
I want to set a timeout to 25-30 minutes of idle time. Should I set both the Forms authentication ticket and SessionState timeout to 30 minutes? ... as well as IIS timeout? Should that change the general slow down of my app?
Please help!
I want also to add a "Remember my password" checkbox ..so that when a user is timed out, they won't need to reenter their credentials .. because i would read from a cookie i save to their PC their log-in and password info!
I also set the timeout in my web.config SessionState tag to 180 minutes.
Users experience a slow down every now and then to my app. Of course there could be a number of reasons but I think 3 hours is far too long to set for idle time. What do you think?
My server has 4gig memory and 2 websites setup on it with one website running terminal services and the other running ASP.Net.
I want to set a timeout to 25-30 minutes of idle time. Should I set both the Forms authentication ticket and SessionState timeout to 30 minutes? ... as well as IIS timeout? Should that change the general slow down of my app?
Please help!
I want also to add a "Remember my password" checkbox ..so that when a user is timed out, they won't need to reenter their credentials .. because i would read from a cookie i save to their PC their log-in and password info!