Timeline for Usability and CSRF tokens
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:32 | history | edited | CommunityBot |
replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
|
|
May 11, 2015 at 16:48 | history | edited | Steve Dodier-Lazaro | CC BY-SA 3.0 |
added 550 characters in body
|
May 11, 2015 at 1:06 | vote | accept | zerkms | ||
May 11, 2015 at 1:05 | comment | added | Steve Dodier-Lazaro | Well that depends whether you have a login form on each page or a dedicated login page! :-) If you want exact advice for your site, then we need to have a 15 minute chat about your user base, your use contexts, and your site's UI... But I hope you get the general idea of what to do from the above :-) | |
May 11, 2015 at 1:03 | comment | added | zerkms | "We need you to log in again because you were inactive for too long" --- you're on the login page already. You cannot "log in again" since you was not yet :-) | |
May 11, 2015 at 0:07 | history | edited | Steve Dodier-Lazaro | CC BY-SA 3.0 |
added 1028 characters in body
|
May 10, 2015 at 23:58 | comment | added | Steve Dodier-Lazaro | Are you able to detect that specific case in Web frameworks? This is really a marginal case, so you could use a more generic formulation "We need you to log in again because you were inactive for too long", and possibly a "learn more" link on your error message where you can explain (in very simple prose!) that sessions expire for security measures and the user was inactive for XX minutes before logging in / since they last logged out. | |
May 10, 2015 at 23:55 | comment | added | zerkms | "Your session has expired because you were inactive for more than XX minutes" --- the thing is that the user hasn't been logged in yet. It's odd to say that to an anonymous user. | |
May 10, 2015 at 23:52 | history | answered | Steve Dodier-Lazaro | CC BY-SA 3.0 |