tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14184] - HttpSession object has confusing behaviour (HttpSession.isNew() )
Date Mon, 04 Aug 2003 20:36:39 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14184>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14184

HttpSession object has confusing behaviour (HttpSession.isNew() )





------- Additional Comments From prhodes@vdsinc.com  2003-08-04 20:36 -------
FWIW, I believe I'm seeing this same bug.  I can call request.getSession() in
one servlet, call request.getSession() later in another servlet, and have the
second session's isNew() method return true.  The session ID's are the same when
this happens, and I do have cookies enabled.

This is with Tomcat 4.1.24

Mime
View raw message