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 ------- Additional Comments From [EMAIL PROTECTED] 2004-01-19 12:36 ------- Aha! I see now. So quickie summary In a single request ... 1) Create a session (which is done by jsp's) 2) Call response.reset() 3) Then the SessionId cookie is not sent to the client (because of the response.reset() (This is the bad part) Since the Session cookie is the responsibility of the container, (I think) it should place the cookie back into the list of headers sent back to the client. A quickie demo: I created a JSP with the content, per previous message. Of this content ... <% session.setAttribute("SessionData","dummy"); response.reset(); %> Then telneted to port 8080 (from a older HEAD build but newer than 4.1.27) and gave this: GET /cowbell.jsp HTTP/1.1 Host: localhost:8080 Connection: close And here was my response: HTTP/1.1 200 OK Content-Length: 2 Date: Mon, 19 Jan 2004 12:30:47 GMT Server: Apache-Coyote/1.1 Connection: close There was no Set-Cookie directive made. I also get the same behavior in 5. I'm swamped with work, but I might be able to look for at a patch tomorrow night. (If this is agreed this is a bug) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
