You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2018. It is now read-only.
My time to live on a session is 60 seconds and my auto remove is 70 seconds.
Problem: With this config, if a clients session gets created at second 0 and never again touched/updated it should expire at second 60. However, because the autoremove function has not yet run if the client makes another request anytime between second 60 and 70 the session ID is returned and the clients session is supposedly valid.
Expected: The session has timed out and the session should be forced to be recreated.
Possible solution: The get functions query should contain a where clause dictating that the expired time has not already passed.
The text was updated successfully, but these errors were encountered:
Nedlinin
added a commit
to Nedlinin/connect-mssql
that referenced
this issue
Sep 23, 2016
@tony-gutierrez : Have seen no action whatsoever and I'm sort of assuming this project has been abandoned by @patriksimek .
I've been pulling the source repo for this PR into my projects in order to have this fix though I do not intend to maintain the repo any further than this one fix.
I've got my session storage setup as follows:
My time to live on a session is 60 seconds and my auto remove is 70 seconds.
Problem: With this config, if a clients session gets created at second 0 and never again touched/updated it should expire at second 60. However, because the autoremove function has not yet run if the client makes another request anytime between second 60 and 70 the session ID is returned and the clients session is supposedly valid.
Expected: The session has timed out and the session should be forced to be recreated.
Possible solution: The get functions query should contain a where clause dictating that the expired time has not already passed.
The text was updated successfully, but these errors were encountered: