in reply to
Re^2: Is your web application really secure? ("CSRF")
in thread Is your web application really secure? ("CSRF")
if i had opened a website with a form in it, let the browser window open and try to send the form the next day i would consider it ok if i then get a message that the token is expired.
If I don't lose my lengthy texts in the form, that would be all right.
But consider you have 10 tabs open, and on the next morning, you re-login in one tab, and then go through the other 9 tabs one after another to click reload. This isn't exactly fun.
Maybe the best (yet complex) solution is this: One could try to fix the expired tokens via Java script (you can read cookies with Java script). If the server still gets expired tokens (which means that Java script was not available), it could check the referer (and that the method was POST, so that no <img> attacks are possible). If there is no referer, the server can still return an error.
This would make using the site more comfortable for those users who have either Java script or referers turned on, while the site is still usable for other users.