On 30/05/17 11:09, Johan Compagner wrote: > Hi, > > if i read this: > > http://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Parallel_deployment > > then i see it will go to the "old" version of a war based on session > information > i guess this is jsessionid? > > So a refresh in the browser or another request with the jsessionid will go > to the version it started with i guess? > > But now i have websockets, if i connect to ##1 first and i have the end > point there > Then i add a ##2 version of the context > then i guess a new user that opens a websocket will go to ##2 > but if the existing user does a refresh in the browser then it will also > suddenly go to ##2 i guess?
It depends. If the URL in the HTTP UPGRADE request includes the session ID, and that session ID is still valid in ##1, then the WebSocket request will be handled by ##1. Mark > > (we have session info over the websocket url like a jsessionid... but that > will not map in the other later version of the context i guess) > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
