On 28/04/2020 07:47, Martin Grigorov wrote: > On Tue, Apr 28, 2020 at 9:11 AM AJ Chen <ajc...@web2express.org> wrote: > >> Anyway to fix it? thanks. -aj >> > > First you need to investigate whether there is a proxy. > Then what kind of proxy. > Then where is its configuration. > Then consult with its manual and see whether there is something > wrong/missng.
I'd recommend taking a step back. Guessing at what might be wrong and then trying to fix the problem you have only guessed at is unlikely to work. Can you recreate the problem? You can't tell if something is fixed if you can't recreate it. Once you recreate the problem then you can start to narrow it down. You need to track what is happening to the session ID. You'll probably need to add some information to the access log, possibly look at some raw network logs and/or look at HTTP headers on the client.. Somewhere in all of the above you should find out where the session ID is getting dropped. Then you need to figure out why. Only then you know why this is happening can you start to think about a solution. Mark > > >> >> >> On Mon, Apr 27, 2020 at 10:54 PM Martin Grigorov <mgrigo...@apache.org> >> wrote: >> >>> Hi, >>> >>> On Tue, Apr 28, 2020 at 2:23 AM AJ Chen <ajc...@web2express.org> wrote: >>> >>>> My web application using tomcat 6 can track user session (cookie by >>>> default) for mobile and PC users in dev environment. But when deployed >> on >>>> cloud server, it fails to track session for some mobile users. meaning, >>>> servlet always creates a new session upon user request. >>>> >>>> Any idea why this happens? >>>> >>> >>> Most probably there is a proxy in front of Tomcat in the cloud >> environment >>> which does not properly forward the JSESSIONID cookie. >>> >>> Martin >>> >>> >>>> >>>> aj >>>> >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
