If they're using Chrome or Mozilla you can guide them through using the developer tools to look at the cookies cached, and even look at the http request and response so they can see whether or not the cookie was sent. Probably other browsers have some similar facility.
On the server side, you could try using Wireshark, but that might be a lot of traffic. Or you could use the CustomRequestLog to log the cookies that you receive so you can see which clients aren't sending them when they should. Regards Jan On Thu, 24 Dec 2020, 23:02 Eze Ikonne, <[email protected]> wrote: > Hi all, > > I have a scenario where, when our webapp is accessed by certain browsers, > the session is null even though it has been initialized prior to been > accessed as below > > HttpServletRequest request = (HttpServletRequest)req; > HttpSession session = request.getSession(false); > > We are running embedded Jetty-9.4.34 > > Is there a mechanism that I could instigate to determine that the browser > is not sending back cookies hence this erratic behavior? I have not > experienced this in > our environment, but one customer is running into this issue. When the > customer uses the Microsoft Edge browser, they are successful. Is there > anything that I could > use to determine why the other browsers are running into this issue? Any > hints and suggestions would be appreciated. > > Thanks, > > Ike > > ===================================================== > Please refer to https://northamerica.altran.com/email-disclaimer > for important disclosures regarding this electronic communication. > ===================================================== > _______________________________________________ > jetty-users mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
