DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28971>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28971 problems if root-context and application-context sets cookies Summary: problems if root-context and application-context sets cookies Product: Tomcat 5 Version: 5.0.24 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I am not sure if this is a new bug (i have used tomcat4 for now and the .24 release is my first try to move to tomcat5). Tomcat (now) sets two cookies - one for the root-context and one for the application context - say (/opsjs). Now on every request two cookies are sent to tomcat - one session-id for the root context and one for the application-context. But it looks like tomcat cant handle this case - maybe only the first cookie is processed and this do not match to the cookie-list for the application-context (just an idea) - so a new session is started and a new cookie sent to the browser. I have had to disable the cookies on the root context. <Context path="" docBase="ROOT" debug="0" cookies="false"/> Then the application works like expected - only one cookie is sent. The definition of the application context is: <Context path="/opsjs" docBase="/u/opsj" crossContext="false" debug="0" reloadable="false" trusted="false" > ... Since another user experienced the same problem i decided to enter this (new) behaviour as critical. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
