This repository has been archived by the owner on Dec 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
vue-resource cause the creation of new session #644
Comments
Does the second request carry a correct cookie header if the server side uses cookie to store session id? |
it is fixed with returning the session id from server and put it in cookie. Project is finished. |
I've come across the same issue, is it a bug? |
Have same problem. I used ExpressJs for server side and then tried to save sessions in Vue side, but server recognizes all requests like different requests. Can someone help with this? In own localhost server saves session and I think it is becaues of vue-resource or maybe because of cors in expressJS |
i met same problem,dont know how to solve |
Same issue here. Looking for solutions or work-arounds. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, when we send da request to our asp.net web api server, it recieves the data successfully and store it in a session, then when we send a second request to get data from session, it creates new session, and returns null data.
When we try with postman, it returns the data which is on the session.
Is that a bug, or are we missing something?
The text was updated successfully, but these errors were encountered: