jwtInterceptor - tokenGetter is not called because of angular caching about angular-jwt HOT 6 CLOSED

Hi. I've noticed this too, but it happens in a very random fashion. Do you know any concrete methods to reproduce this? When does Angular cache the headers?

from angular-jwt.

It's hard to define steps, but it happens really often.

from angular-jwt.

You could be right, by removing the header check the issue seemed to vanish. But it's strange nonetheless.

from angular-jwt.

I take back everything. My issue was different: in the tokenGetter method I checked if the token has expired and only then did I call the refresh API method. When the client clock and the server clock weren't in sync it could happen, that the client sees an expired token as valid and would not call the refresh method.

from angular-jwt.

Hi, maybe I am a bit late to the party. Is the issue solved now? Does adding a random string to the end of the URL help?

from angular-jwt.

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! 🙇‍♂️

from angular-jwt.