You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When posting issues, please include the following information to speed up the troubleshooting process:
Version: 1.2.1, using redux-auth-token
the token header (defaults to "access-token") is blank if the token doesn't change. Not blank if the token does change.
With the configuration change_headers_on_each_request = true old libraries like redux-auth-token assume that a token will come in with every request. Instead it is only set after the old token expired. There are a bunch of requests for which the token is blank, and the library just expects the client to use the lat token it provided.
This is definitely something that can be worked around (though had to rip open the library) but would be really ideal if we could just not return blank headers. Just return the same token if it isn't changed, and return a new one if appropriate.
Sidenote: Shouldn't every request get a new token anyways?
The text was updated successfully, but these errors were encountered:
When posting issues, please include the following information to speed up the troubleshooting process:
the token header (defaults to "access-token") is blank if the token doesn't change. Not blank if the token does change.
With the configuration
change_headers_on_each_request = true
old libraries like redux-auth-token assume that a token will come in with every request. Instead it is only set after the old token expired. There are a bunch of requests for which the token is blank, and the library just expects the client to use the lat token it provided.This is definitely something that can be worked around (though had to rip open the library) but would be really ideal if we could just not return blank headers. Just return the same token if it isn't changed, and return a new one if appropriate.
Sidenote: Shouldn't every request get a new token anyways?
The text was updated successfully, but these errors were encountered: