This version supports polling requests as I outlined above. If the session timeout is 20 minutes and the user is ACTIVE on your page for longer than that, the session shouldn’t expire. Once they become idle for the configurable amount, the polling pauses and the warning bar kicks in.

There are a few measures in place to ensure requests don’t build up with setInterval. The response returned must match the serverResponseEquals parameter, and you can configure a maximum number of failed requests with the failedRequests param. If the request failed (either timed out or a 500, 404, etc code is returned) OR the server’s response did not match serverResponseEquals “failedRequests” times, the code aborts.

I still have some cleaning up to do and want to make it more flexible, but for the purposes of this article and demo, it is good to go.

This version supports polling requests as I outlined above. If the session timeout is 20 minutes and the user is ACTIVE on your page for longer than that, the session shouldn’t expire. Once they become idle for the configurable amount, the polling pauses and the warning bar kicks in.

There are a few measures in place to ensure requests don’t build up with setInterval. The response returned must match the serverResponseEquals parameter, and you can configure a maximum number of failed requests with the failedRequests param. If the request failed (either timed out or a 500, 404, etc code is returned) OR the server’s response did not match serverResponseEquals “failedRequests” times, the code aborts.

I still have some cleaning up to do and want to make it more flexible, but for the purposes of this article and demo, it is good to go.

Indeed. Technically, this script only implements the UI portion of the logic. I am working on a version that polls the server every XX seconds (minutes?) to keep the session alive while the user is considered “active”. Once the idle state is detected the polling stops and the warning kicks in.

Indeed. Technically, this script only implements the UI portion of the logic. I am working on a version that polls the server every XX seconds (minutes?) to keep the session alive while the user is considered “active”. Once the idle state is detected the polling stops and the warning kicks in.

1. Session timeout=20 minutes
2. idleTimeout shows when 5 minutes is left.

Now, if I just move the mouse or type some text in a box it does not reset the session on the server. so…10 minutes later I leave the desk, session has 10 minutes left but the idleTimout popup will now show for another 15 minutes. Meaning the session will have already expired.

What do I do?

1. Session timeout=20 minutes
2. idleTimeout shows when 5 minutes is left.

Now, if I just move the mouse or type some text in a box it does not reset the session on the server. so…10 minutes later I leave the desk, session has 10 minutes left but the idleTimout popup will now show for another 15 minutes. Meaning the session will have already expired.

What do I do?

It’s a nice script. The only addition I’d suggest (and which I did) was to add a second .animate() once the expired message is shown. That way there’s time enough to read the end message before it redirects.