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=8100>. 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=8100 Session Tracking and HttpURLConnection [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Other |Windows NT/2K Summary| Session Tracking and |Session Tracking and |HttpURLConnection |HttpURLConnection ------- Additional Comments From [EMAIL PROTECTED] 2002-04-15 13:54 ------- For the situation explained earlier, I have one more point to mention. I ran the client Web Application in Tomcat 3.2 and the server Web application in Tomcat 4.0, that works. If both the client and server web application are hosted by 3.2, that works. The application fails if the Client web application is 4.0. To maintain the "server web application's session id", I am using the following code in the "client web application": Cookie c =new Cookie("JSESSIONID",jsessionid); c.setMaxAge(3600000); resp.addCookie(c); Where jsessionid is a part of the response stream as a result of posting the message through HttpURLConnection. Commenting this code out would result in both Tomcat 3.2 and tomcat 4.0 not to work with my application, whereas with the above lines in a servlet, "tomcat 3.2 client webapp" works but not "tomcat 4.0 webapp". -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
