|Re: Multiple RAP Sessions lead to Session Timeout [message #1783990 is a reply to message #1783988]
||Wed, 21 March 2018 09:22
| Sebastian Ganser
Registered: August 2014
My assumption is that jetty is using the cookie to get/ask for the correct http session (serverside), but there is only one cookie for every host. In my case there are rap-applications running on the same host and everytime i connect to an rap app with the same browser a cookie is placed for the host (app 1 url 192.168.1.10:8081/test -> host:192.168.1.10). If i connect to another session (app 2 url 192.168.1.10:8082/test2 -> host: 192.168.1.10) the host is still the same, but jetty already generated a new sessionid, which is placed as cookie for the same host. So the cookie will be overwritten. After switching to the tab with the first opened rap app jetty will read the sessionid in the cookie and ask the session handler for the correct session, which cant be provided, because the id belongs to the session of the second rap-application and therefore rap signals a session timeout.
Could you give me your thoughts on that and maybe tell me what handler you are using for your rap demo apps?
I forgot to mention that i use RAP in combination with E4 (3.2.0). A snippet/project will be provided as soon as possible.
Powered by FUDForum
. Page generated in 0.02729 seconds