I started here:
What is the purpose of the holes marked "Do Not Cover" on hard drives?

On this computer, I was logged into the network on Meta and SO, but not yet on SU. I wanted to cast an upvote, so I clicked "Log in", which led me to the regular login page with this url:

I clicked facebook login (like I always do), which led to this page:

It told me that my request was "suspicious" and "could not be completed". But, in spite of that message , my request apparently was processed. You can see from the freehand circle in the screenshot that it did in fact log me in (and when I went back to the original question and refreshed the page, I was now logged in).

enter image description here

As far as I can tell, I did nothing out of the ordinary here. Not a big deal at all, but definitely seems like a bug to me.

  • Similar issue here May 17, 2013 at 19:01
  • 3
    I get that all the time when SE tries to auto-log me in when I visit a SE site, however I'm too impatient or don't realize it, and click the "Login" button before it finishes logging me in from the background
    – Rachel
    May 17, 2013 at 19:01
  • @Rachel, hmm. That's probably related, but in this case that's not exactly what happened. I spent a good 10 minutes on the original page reading the question/answers before I clicked log in. The "automatically logged in" box never popped up. But yes, it could be that I was already logged in in the background but the bug was just with the notification.
    – Ben Lee
    May 17, 2013 at 19:19

1 Answer 1


This will be fixed in the next deploy.

The root cause was global log in completing in the backend, but you submitting the log in form before it forced a refresh on the client side. This looks to use like you're submitting an incorrect XSRF token, when actually you're just submitting the one we gave you before you logged in.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .