Hi All,
I have a webpage named default.aspx which has a button which on clicking opens up a new window named Login.aspx. When login is successful, Main.aspx opens on same window of Login.aspx. Now my question is, if I leave the window of default.aspx idle and do
nothing and then I click on that button it should not timeout ever. But right now, we have some webpages designed in html as custom error pages so when the timeout has been reached it just loads the error404.html. I am not able to avoid the timeout when i
deploy it in some server and then open up from my desktop. I am aware of the fact by giving a value of timeout=1440 in sessionstate tag in web.config may solve the issue but the thing is a little complex. In Main.aspx, as soon as the browser will trigger an
event for onblur, it will load a window which has 30 seconds of time and then closes the application. I thought this would be the best approach and later I saw that the javascript for onblur would n ...
Go to the complete details ...