Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh token and http asynchronus queue #57

Closed
girod opened this issue Jul 26, 2015 · 3 comments
Closed

Refresh token and http asynchronus queue #57

girod opened this issue Jul 26, 2015 · 3 comments

Comments

@girod
Copy link

girod commented Jul 26, 2015

There is a bug when we use getrefreshtoken if the page has sent multiple asynchronus http requests. Because all the http requests 'refresh_token' are sent with the first access token ... The first request is ok : we get the new access token but the next requests in the queue use the old access token. So we get a 401 error ...

@pashamesh
Copy link

+1

@ruipenso
Copy link
Member

ruipenso commented Feb 8, 2016

The changes introduced in #77 solves this issue. Closing it.

@ruipenso ruipenso closed this as completed Feb 8, 2016
@ruipenso
Copy link
Member

These chances was reverted and re-introduce in a major version (4.0.0) due to BC. See this comment for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants