What steps will reproduce the problem?
1. Use Tomcat 6.0.24
2. Run an application behind a load-balancer with sticky sessions
3. Public visible path differs from application context path
4. Use the application, we will receive a session-id cookie locked to a
specific node
5. Shutdown the node
6. Reload the page, we will be directed to another node
7. Memcached Sessionmanager of the node will take over the session
8. Memcached Sessionmanager sends a Set-Cookie response to the client with the
new session id, but it ignores the cookie path configured in context.xml, but
uses the application context path instead
9. The browser ignores the new cookie as it points to the wrong path. Browser
continues to operade with the old cookie, which is wrong
What is the expected output? What do you see instead?
If there is a sessionCookiePath configured in web.xml, memcached should use
this path, and not the context-path for the new cookie
What version of the product are you using? On what operating system?
Tomcat 6.0.24
Memcached Session Manager 1.8.3
Please provide any additional information below.
-
Original issue reported on code.google.com by mirkosertic42@gmail.com on 25 Feb 2015 at 11:15
Original issue reported on code.google.com by
mirkosertic42@gmail.comon 25 Feb 2015 at 11:15