Vuejs: Routes are accessible even after deleting a token
up vote
0
down vote
favorite
I have a very strange behaviour when I log out from my app. Some inner links (from a user's panel, for example) are still accessible even after I logged out and deleted a token. And some links are not. Do you have any ideas how I can prevent this behaviour?
javascript vue.js authorization
asked Nov 22 at 11:06
Olga B
10613
add a comment |
up vote
0
down vote
favorite
I have a very strange behaviour when I log out from my app. Some inner links (from a user's panel, for example) are still accessible even after I logged out and deleted a token. And some links are not. Do you have any ideas how I can prevent this behaviour?
javascript vue.js authorization
asked Nov 22 at 11:06
Olga B
10613
Generally with a navigation guard that is applied globally and looks at the route meta data. Without any code it is impossible to tell why you see odd behaviour like that though.
– Sumurai8
Nov 22 at 11:09
Do you use guards? Maybe some code sample of your routes?
– Konstantin Kudelko
Nov 22 at 11:09
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a very strange behaviour when I log out from my app. Some inner links (from a user's panel, for example) are still accessible even after I logged out and deleted a token. And some links are not. Do you have any ideas how I can prevent this behaviour?
javascript vue.js authorization
asked Nov 22 at 11:06
Olga B
10613
I have a very strange behaviour when I log out from my app. Some inner links (from a user's panel, for example) are still accessible even after I logged out and deleted a token. And some links are not. Do you have any ideas how I can prevent this behaviour?
javascript vue.js authorization
javascript vue.js authorization
asked Nov 22 at 11:06
Olga B
10613
asked Nov 22 at 11:06
Olga B
10613
asked Nov 22 at 11:06
Olga B
10613
asked Nov 22 at 11:06
Olga B
10613
asked Nov 22 at 11:06
Olga B
10613
10613
Generally with a navigation guard that is applied globally and looks at the route meta data. Without any code it is impossible to tell why you see odd behaviour like that though.
– Sumurai8
Nov 22 at 11:09
Do you use guards? Maybe some code sample of your routes?
– Konstantin Kudelko
Nov 22 at 11:09
add a comment |
Generally with a navigation guard that is applied globally and looks at the route meta data. Without any code it is impossible to tell why you see odd behaviour like that though.
– Sumurai8
Nov 22 at 11:09
Do you use guards? Maybe some code sample of your routes?
– Konstantin Kudelko
Nov 22 at 11:09
Generally with a navigation guard that is applied globally and looks at the route meta data. Without any code it is impossible to tell why you see odd behaviour like that though.
– Sumurai8
Nov 22 at 11:09
Generally with a navigation guard that is applied globally and looks at the route meta data. Without any code it is impossible to tell why you see odd behaviour like that though.
– Sumurai8
Nov 22 at 11:09
Do you use guards? Maybe some code sample of your routes?
– Konstantin Kudelko
Nov 22 at 11:09
Do you use guards? Maybe some code sample of your routes?
– Konstantin Kudelko
Nov 22 at 11:09
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
So I solved my problem by using axios interceptors. I check if the error status in 401 (Unauthorised) and push router to the login page.
axiosInstance.interceptors.response.use(null, (error) => {
if (error.response.status === 401) {
config.token = null;
router.push({ name: 'login' });
}
if (error.response.status === 404) {
router.push({ name: 'error' });
}
return Promise.reject(error);
});
answered Nov 23 at 7:28
Olga B
10613
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
So I solved my problem by using axios interceptors. I check if the error status in 401 (Unauthorised) and push router to the login page.
axiosInstance.interceptors.response.use(null, (error) => {
if (error.response.status === 401) {
config.token = null;
router.push({ name: 'login' });
}
if (error.response.status === 404) {
router.push({ name: 'error' });
}
return Promise.reject(error);
});
answered Nov 23 at 7:28
Olga B
10613
add a comment |
up vote
0
down vote
accepted
So I solved my problem by using axios interceptors. I check if the error status in 401 (Unauthorised) and push router to the login page.
axiosInstance.interceptors.response.use(null, (error) => {
if (error.response.status === 401) {
config.token = null;
router.push({ name: 'login' });
}
if (error.response.status === 404) {
router.push({ name: 'error' });
}
return Promise.reject(error);
});
answered Nov 23 at 7:28
Olga B
10613
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
So I solved my problem by using axios interceptors. I check if the error status in 401 (Unauthorised) and push router to the login page.
axiosInstance.interceptors.response.use(null, (error) => {
if (error.response.status === 401) {
config.token = null;
router.push({ name: 'login' });
}
if (error.response.status === 404) {
router.push({ name: 'error' });
}
return Promise.reject(error);
});
answered Nov 23 at 7:28
Olga B
10613
So I solved my problem by using axios interceptors. I check if the error status in 401 (Unauthorised) and push router to the login page.
axiosInstance.interceptors.response.use(null, (error) => {
if (error.response.status === 401) {
config.token = null;
router.push({ name: 'login' });
}
if (error.response.status === 404) {
router.push({ name: 'error' });
}
return Promise.reject(error);
});
answered Nov 23 at 7:28
Olga B
10613
answered Nov 23 at 7:28
Olga B
10613
answered Nov 23 at 7:28
Olga B
10613
answered Nov 23 at 7:28
Olga B
10613
10613
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53429594%2fvuejs-routes-are-accessible-even-after-deleting-a-token%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
Generally with a navigation guard that is applied globally and looks at the route meta data. Without any code it is impossible to tell why you see odd behaviour like that though.
– Sumurai8
Nov 22 at 11:09
Do you use guards? Maybe some code sample of your routes?
– Konstantin Kudelko
Nov 22 at 11:09