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() ) Summary: HttpSession object has confusing behaviour (HttpSession.isNew() ) Product: Tomcat 4 Version: 4.1.12 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Servlet & JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I don't know if this would qualify as a bug. But it's definitely a behaviour change from 4.0.3 to 4.1.12. Two examples: 1) When I go from servlet A to servlet B, and printout the session ID in both servlets, they are the same value. But, if I do a session.isNew() in session B, the return value is true. My browser is cookie enabled and I'm sure the session has not expired. This did not happen in Tomcat 4.0.3. 2) The values from the following lines are not the same. Again, the browser is cookie enabled and the session has not expired. myRequest.getSession().getId(); myRequest.getRequestedSessionId(); The values are the same when I run the code in Tomcat 4.0.3. Has there been change between 4.0.3 and 4.1.12 that would result in the above behaviour change? -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
