the session id cookie sent with the request and serving response based on the id. in my site all users sending requests to the same host and urls are also same for individual tasks (like upload, search, etc). based on user id at server i am differentiating. but problem is when different users are logged in the same browser in different tabs, session id cookie is getting overridden or new session id cookie is getting appended to the browser request as all share the same host. how to tackle this issue? using HttpOnly cookie so can't do anything at client end. one way is using path name with cookie. but how do i get that at browser to add to the request path?
This is by design, cookies are not isolated between tabs. All you really have is memory that’s isolated, local and session storage are shared as well. I think users are pretty accustomed to this and understand the various browser mechanisms for isolation (private browsing, personas for FF, etc)
yes. one way is setting cookie Path to a random identifier and appending that identifier to all request urls. to append that, the same identifier can be sent to browser with response header or body. but that will be much complicated.
Обсуждают сегодня