Open davidben opened 11 years ago
I think this might be a problem on the client actually. Nothing shows up in nginx's logs. Maybe some CORS caching stupid. Except I can't find the error that would have triggered it.
Hit it on my phone. Seems to be fixed by killing Chrome. I think this is some kind of broken CORS caching, yeah.
Okay, what?