Open fjaguero opened 10 years ago
Mmm… this might be related with SSL connection cache on my nginx deployment, or even spdy, that reuses the connection so express thinks (correctly) that it's the same user and does not create new tokens to connect to twitter.
I will try to reproduce it in my environment
After cancelling the authentication, twitter throws the following error: "It looks like that already used the token information you provided".
Steps to reproduce:
Launched in Firefox OS 1.4 simulator.