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 Summary: ServletResponse#reset() method and cookie session control problem on tomcat4.1.24 Product: Tomcat 4 Version: 4.1.24 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The following problem was encountered. I was wondering if this behavior is specification. 1)I set "true" as value of 'cookeis' attribute of 'context' tag in server.xml. (default) 2)I called following JSP in the web application. -------------------------- ..... <% session.invalidate(); session=request.getSession(); session.setAttribute("SessionData","dummy"); response.reset(); %> ..... -------------------------- 3)I found that 'session.getAttribute("SessionData")' returned null at the next request from the same browser. It seems that the session was lost. Originally, 'session' and 'reset() method' should not be related but they seem to be related. I think that this problem originates in the following operation. org.apache.coyote.tomcat4.CoyoteRequest.java doGetSession() method ---------------------------- ..... ((HttpServletResponse) response).addCookie(cookie); ..... ---------------------------- This code set 'Set-Cookie' header to the response. Next the 'Set-Cookie' header has been cleared by the reset() method. Then session maintenance went wrong at the next request. In fact, this has generated on the error page and evasion is difficult. (I don't use reset() method directly but exception occurred after create new session. reset() method is called indirectly to handle this exception from tomcat.) This problem occurred also on tomcat5 but happened neither on weblogic8 nor WebSphere5. Is this behavior specification ? If this is not as an intention, could I have the correction of tomcat(maybe coyote) ? regards, Naru Hayashi from Japan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
