Closed zorn-v closed 2 years ago
Currently redirect to "login" route does not perform on "invalid token request" as invalid object passed to router ({redirect: {path: '/login'}} with default options). Actual redirect is performing on next route change now (as token cleared).
{redirect: {path: '/login'}}
Ok fixed in 4.1.8, thx :-)
4.1.8
websanova
commented
2 years ago
Currently redirect to "login" route does not perform on "invalid token request" as invalid object passed to router (
{redirect: {path: '/login'}}with default options). Actual redirect is performing on next route change now (as token cleared).