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 26183] - ServletResponse#reset() method and cookie session control problem on tomcat4.1.24
Date Mon, 19 Jan 2004 02:53:43 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=26183>.
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=26183

ServletResponse#reset() method and cookie session control problem on tomcat4.1.24

hayashin@ist.fujitsu.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From hayashin@ist.fujitsu.com  2004-01-19 02:53 -------
Hello,
Thank you for response and I'm sorry for Reopen bug.

My point is 'response.reset()', not 'session.invalidate()'.
This problem occur when 'response.reset()' method call after create new session.
This happen also when the first access to session, access to session after 
session timeout ...
So for other example, the first request, call following JSP(JSP only for easy).
------------
....
<%
session.setAttribute("SessionData","dummy");
response.reset();
%>
....
------------
And the next request, 'session.getAttribute("SessionData")' return null.

The reason is as having explained last time.

Is this behavior specification ?

regards,
Naru Hayashi from Japan

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message