rietveld: Dataloss with "Invalid XSRF token" error
If you leave a review page open too long (24+ hours?) and then try to write a
reply, after submission you get "Invalid XSRF token." Then if you hit back,
your reply is gone, because it was composed in some AJAXy box that no longer
appears.
There are several possible mitigations.
First, the full submitted reply (or other mail) could be pasted on the "invalid
xsrf token" page so you could copy it and paste it back in when going back.
Second, the page could be structured such that when you go back, the browser
can successfully persist the relevant form data.
Third, the page could do JS requests every few hours to keep the token alive.
Original issue reported on code.google.com by pkasting@chromium.org on 12 Jan 2012 at 8:39
About this issue
- Original URL
- State: closed
- Created 12 years ago
- Comments: 16