Force jwtInterceptor to call tokenGetter #61
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
November 20, 2015 17:08
…option set to true, then interceptor will ignore any cached or previously set authorization header and call tokenGetter for each request.
|
Hey there, sorry this has been left sitting for a year. We're catching up on some older issues and PRs now. We've changed some things since you sent this in. Would you be interested in rebasing? Thanks very much for your PR 🙌 |
|
any update? |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default
tokenGetterwon't be called if authorization header has already been set. Sometimes angular caches headers andtokenGetteris not called. To force jwtInterceptor calltokenGetterfor each request setforceHeadersUpdateparameter totrue.Pull request for issue