You may want to check how your browser interprets the encoded URL. Compare what has been sent to the browser and what went back towards Tomcat. I was assisting another person the other day and we found out that the cookie is mangled, the "~" was not urlencoded to "%7.." something. I am not saying thats the cause, just check and see if you can observe such characteristics. You can enable RequestDumperValve to see these.
--- Tim Funk <[EMAIL PROTECTED]> wrote: > By default JSP's need to be told to *not* ask for a > session via > <[EMAIL PROTECTED] session='false'%> > > Otherwise - it sounds like a cookie setting issue > that the client isn't > remembering the sessionid. > > -Tim > > LAM Kwun Wa Joseph wrote: > > > I have implemented a simple HttpSessionListener > dumping every new session > > created. I found that my Tomcat (tried on 5.0.2x > and 5.5.4) will always > > create a new session for every HTTP request, even > if the JSP page doesn't > > request for session and the HTTP client doesn't > use cookie nor post any > > session ID (e.g. direct telnet to port 80). > > > > Are there any config params that relate to this? > Thanks! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
