-
Notifications
You must be signed in to change notification settings - Fork 15
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
Default headers not being attached to the requests #6
Comments
You're setting the token on local storage or in other base? After the login you need to record the token in some place |
hi lenonardo, I have same problem.Refresh token header doesnt attach to request.So I can not get refresh token at server side. Is this normal? Request URL:http://localhost:8080/xx/refreshtoken/ } module:
};
}); authConfig.getConfig().globalHeaders.push({'screenResolutionWidth': window.width}); let jwtHttp = new JwtHttp( console.log("jwtHttp module load" +JSON.stringify(jwtHttp) ); |
At login, I set both refresh token and id token at local storage |
I think it's fixed somehow. Don't know exactly what I did |
I have a problem now, that the endPoint defined in the options is called in every request. Is this normal behaviour? |
Hi, I copied your exact same code and attached it to my project, but when I call the JwtHttp methods (put, get, post), the Authorization header doesn't seem to be attached to the request.
What can be the problem?
The text was updated successfully, but these errors were encountered: