Changes between Version 2 and Version 3 of Ticket #24280, comment 4
- Timestamp:
- Mar 23, 2015, 4:36:28 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24280, comment 4
v2 v3 4 4 5 5 A temporary fix for this seems to be to nuke the Chrome cookie. In corresponding with a user, I verified that a CSRF token in fact is populated in the form before receiving the error. 6 7 Armed with the value of that token or the stale cookie, is there something I can do to further debug this problem?