Trustmaster |
|
---|---|
It happens when:
[list=1] It is request and cookie forgery protection: a secret key changes on every request and the cookie is changed every request too. If you send a request but your cookie hasn't updated yet, the site considers that as request forgery and breaks the session. It is quite a high wall for CSRF and XSS attackers, but as I see it causes problems for many users so, seems like unfortunately we will have to lower our defence in favor of user comfort. May the Source be with you!
|