How to refresh the session timeout when the page is on alive

Question

1.00/5 (1 vote)

See more:

Hello,

The timeout has been declared like below,

sessionstate timeout="1" mode="InProc"

My requirement is, when the user is not doing any action on the page, then the page should get timeout and redirect to log in page. Else, for each activity the timeout should be refreshed.

Currently the application is working such a way that, the session will be expired, regardless of page alive or not. That means if the page is loaded and after 20 minutes, the page gets time out.

Please advise me for this issue.
Thanks in advance

Posted 5-Jul-15 19:56pm

DPM20

Updated 8-Jul-15 1:28am

v3

Add a Solution

Comments

Suvendu Shekhar Giri 6-Jul-15 2:47am

Can you share the respective code block in your web.config? or, where ever you have set the session timeout value?

DPM20 6-Jul-15 3:51am

Session has already been included in the Web.config,

sessionState timeout="20" mode="InProc"

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2015-07-05T20:47:00

Solution 1

The session is maintained at the server, but dropdowns and textboxes are handled locally by the client: unless the client talks to the server regularly, the session object will time out, even if the user is busy filling in his page. You could make each user action trigger a server event, but that would be rather messy and will slow the client down significantly if you don't do it properly.

Normally, a session timeout is set to around 20 minutes - so if your client is taking longer than this, you might want to extend that: it's not recommended though, as each session object takes resources from the server to maintain.

Posted 5-Jul-15 20:47pm

OriginalGriff

Comments

DPM20 6-Jul-15 3:55am

i have already included the timeout in web.config,
sessionState timeout="20" mode="InProc"

I am wondering if drop down is clicked, values are populating from db, that means it triggers a server side hit. So this action should extend the timeout right?

OriginalGriff 6-Jul-15 4:05am

Not necessarily: depends how you are doing things.
Are your dropdowns linked in the HTML, or at the server via C#?

DPM20 6-Jul-15 4:07am

Server side only

OriginalGriff 6-Jul-15 4:29am

In which case, opening the dropdown won't cause a post back, and the session timeout won't restart.

You might have to consider adding Javascript code to detect user changes and post back just to trigger the reset. (Yeuch!)

But if you have twenty minutes, the user should ok, normally.
How quick is the session timing out?