-
Notifications
You must be signed in to change notification settings - Fork 27
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
Install and setup feathers-vuex #292
Conversation
Fixed conflicts |
Check passed 💃 |
@roschaefer this seems ready :3 |
df84257
to
992c08b
Compare
I think we could merge that, too |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
session on the server side (SSR) is not destroyed which leads to the following scenario:
- login as admin ([email protected])
- logout
- login as regular user ([email protected])
- refresh page after you are logged in
- see that you are logged in again as the last user (admin) instead of your last loggin (user)
You need to remove that session also on the server side, maybe there is a cookie still flying around in the browser which is then send on SSR and the backend responds with the logged in user from the token in the cookie.
``` session on the server side (SSR) is not destroyed which leads to the following scenario: 1. login as admin ([email protected]) 2. logout 3. login as regular user ([email protected]) 4. refresh page after you are logged in 5. see that you are logged in again as the last user (admin) instead of your last loggin (user) You need to remove that session also on the server side, maybe there is a cookie still flying around in the browser which is then send on SSR and the backend responds with the logged in user from the token in the cookie. ``` This is not possible now, as the lazy-loading happens with `app.$api` and not the socket.
Covered in #218 |
and configure it at runtime, yay!