https://issues.apache.org/bugzilla/show_bug.cgi?id=44585
Summary: mod_jk resolves jvmRoute first from the url instead from
the cookies
Product: Tomcat 5
Version: Unknown
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Native:JK
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Hi,
I have issue with sticky session and the way the mod_jk tries to resolve
jvmRoute!
Imagine this example: we have two tomcat with two applications A and B deployed
on both tomcat. The application A is deployed within root context (context path
/) and B is within context /b.
User makes request to the application B. The application B makes new http
session, and redirects the browser to the application A. If this request is
served by first tomcat; browser will receive: Cookie: jsessionid=xxx.jvmRoute_1
(path /b) and HTTP Response: code 302, Location=http://host/a.
Browser will make request: GET http://host/a (there is no cookie because the
cookie jsessionid=xxx.jvmRoute_1 have context path /b).
Mod_jk decide to send this request to second tomcat. The application A makes
new http session and redirect the browser to the application A
(request.encodeURL is used). The browser receives: Cookie:
jsessionid=yyy.jvmRoute_2 (path /) and HTTP Response: code 302,
Location=http://host/b/toto;jsessionid=yyy.jvmRoute_2.
In this case browser will send HTTP Get:
http://host/b/toto;jsessionid=yyy.jvmRoute_2 with cookies:
jsessionid=xxx.jvmRoute_1,jsessionid=yyy.jvmRoute_2. When mod_jk resolves
jvmRoute it will find that this request have to be sent to the second tomcat,
and the session made in the first request to the application B will be lost
(imagine if this session is about authentication).
Is it normal that mod_jk when try to resolve jvmRoute check firs the jsession
id in the url path instead in the cookies?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
