Axios Intercept not applying token from localStorage on first call
So I have a problem with my Vue application, where my axios intercept doesn't apply the authorization token.
axios.interceptors.request.use(config => {
let token = localStorage.getItem("jwt_token")
console.log("Token is: ", token)
console.log(typeof token)
if (token) {
axios.defaults.headers.Authorization = `Bearer ${token}`
}
console.log(config)
return config
});As you can see I've console logged my Token, before applying it to the Auth header, however this is what I get in my console log.
On the first request the token prints just fine, but inside the header, it's set as null and I get a 422 response
on the second API request, my token applies just fine, and I receive data back.
javascript vue.js axios
asked Nov 26 '18 at 5:13
OllieOllie
182
add a comment |
So I have a problem with my Vue application, where my axios intercept doesn't apply the authorization token.
axios.interceptors.request.use(config => {
let token = localStorage.getItem("jwt_token")
console.log("Token is: ", token)
console.log(typeof token)
if (token) {
axios.defaults.headers.Authorization = `Bearer ${token}`
}
console.log(config)
return config
});As you can see I've console logged my Token, before applying it to the Auth header, however this is what I get in my console log.
On the first request the token prints just fine, but inside the header, it's set as null and I get a 422 response
on the second API request, my token applies just fine, and I receive data back.
javascript vue.js axios
asked Nov 26 '18 at 5:13
OllieOllie
182
add a comment |
So I have a problem with my Vue application, where my axios intercept doesn't apply the authorization token.
axios.interceptors.request.use(config => {
let token = localStorage.getItem("jwt_token")
console.log("Token is: ", token)
console.log(typeof token)
if (token) {
axios.defaults.headers.Authorization = `Bearer ${token}`
}
console.log(config)
return config
});As you can see I've console logged my Token, before applying it to the Auth header, however this is what I get in my console log.
On the first request the token prints just fine, but inside the header, it's set as null and I get a 422 response
on the second API request, my token applies just fine, and I receive data back.
javascript vue.js axios
asked Nov 26 '18 at 5:13
OllieOllie
182
So I have a problem with my Vue application, where my axios intercept doesn't apply the authorization token.
axios.interceptors.request.use(config => {
let token = localStorage.getItem("jwt_token")
console.log("Token is: ", token)
console.log(typeof token)
if (token) {
axios.defaults.headers.Authorization = `Bearer ${token}`
}
console.log(config)
return config
});As you can see I've console logged my Token, before applying it to the Auth header, however this is what I get in my console log.
On the first request the token prints just fine, but inside the header, it's set as null and I get a 422 response
on the second API request, my token applies just fine, and I receive data back.
axios.interceptors.request.use(config => {
let token = localStorage.getItem("jwt_token")
console.log("Token is: ", token)
console.log(typeof token)
if (token) {
axios.defaults.headers.Authorization = `Bearer ${token}`
}
console.log(config)
return config
});axios.interceptors.request.use(config => {
let token = localStorage.getItem("jwt_token")
console.log("Token is: ", token)
console.log(typeof token)
if (token) {
axios.defaults.headers.Authorization = `Bearer ${token}`
}
console.log(config)
return config
});javascript vue.js axios
javascript vue.js axios
asked Nov 26 '18 at 5:13
OllieOllie
182
asked Nov 26 '18 at 5:13
OllieOllie
182
asked Nov 26 '18 at 5:13
OllieOllie
182
asked Nov 26 '18 at 5:13
OllieOllie
182
asked Nov 26 '18 at 5:13
OllieOllie
182
182
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
At this stage, the config object passed to your interceptor has already been merged with the defaults so assigning the token to axios.defaults.headers.Authorization isn't going to affect the current request's config.
With that in mind, all you need from your interceptor is...
config => {
let token = localStorage.getItem("jwt_token")
config.headers = Object.assign({
Authorization: `Bearer ${token}`
}, config.headers)
return config
}
I've used Object.assign() with the current headers last so as not to overwrite any existing Authorization header.
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53475086%2faxios-intercept-not-applying-token-from-localstorage-on-first-call%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
At this stage, the config object passed to your interceptor has already been merged with the defaults so assigning the token to axios.defaults.headers.Authorization isn't going to affect the current request's config.
With that in mind, all you need from your interceptor is...
config => {
let token = localStorage.getItem("jwt_token")
config.headers = Object.assign({
Authorization: `Bearer ${token}`
}, config.headers)
return config
}
I've used Object.assign() with the current headers last so as not to overwrite any existing Authorization header.
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
add a comment |
At this stage, the config object passed to your interceptor has already been merged with the defaults so assigning the token to axios.defaults.headers.Authorization isn't going to affect the current request's config.
With that in mind, all you need from your interceptor is...
config => {
let token = localStorage.getItem("jwt_token")
config.headers = Object.assign({
Authorization: `Bearer ${token}`
}, config.headers)
return config
}
I've used Object.assign() with the current headers last so as not to overwrite any existing Authorization header.
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
add a comment |
At this stage, the config object passed to your interceptor has already been merged with the defaults so assigning the token to axios.defaults.headers.Authorization isn't going to affect the current request's config.
With that in mind, all you need from your interceptor is...
config => {
let token = localStorage.getItem("jwt_token")
config.headers = Object.assign({
Authorization: `Bearer ${token}`
}, config.headers)
return config
}
I've used Object.assign() with the current headers last so as not to overwrite any existing Authorization header.
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
At this stage, the config object passed to your interceptor has already been merged with the defaults so assigning the token to axios.defaults.headers.Authorization isn't going to affect the current request's config.
With that in mind, all you need from your interceptor is...
config => {
let token = localStorage.getItem("jwt_token")
config.headers = Object.assign({
Authorization: `Bearer ${token}`
}, config.headers)
return config
}
I've used Object.assign() with the current headers last so as not to overwrite any existing Authorization header.
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
edited Nov 26 '18 at 5:50
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
answered Nov 26 '18 at 5:23
PhilPhil
97k11139158
97k11139158
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
add a comment |
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
Fantastic, thank you. I was about to resort to setting the headers in the store on the login action, but I much prefer this way.
– Ollie
Nov 26 '18 at 5:31
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53475086%2faxios-intercept-not-applying-token-from-localstorage-on-first-call%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
