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
open tab in Chrome. type localhost:3000/account. You get login as expected
type bob, secret, do not check 'remember me'. You get home as expected
go to /account, go to /home
Close tab, close Chrome. (Do not restart server.)
Restart Chrome, open new tab, type localhost:3000/account
You get bob's account info.
Chrome's dev tools show Express' connect.sid cookie as Expires=Session. However it's value after the Chrome restart is the same as before. I would have expected Chrome to delete it and then Express to create a new value.
What am I missing here? Is there any way to require a login when Chrome is restarted? Thanks.
These steps show the issue:
Chrome's dev tools show Express' connect.sid cookie as Expires=Session. However it's value after the Chrome restart is the same as before. I would have expected Chrome to delete it and then Express to create a new value.
What am I missing here? Is there any way to require a login when Chrome is restarted? Thanks.
Edit:
This looks similar: http://stackoverflow.com/questions/10957800/google-chrome-session-expire-null-not-working
I did not see anything in the Windows7 task manager that looked Chrome' or addon'ish.
The text was updated successfully, but these errors were encountered: