[
https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl...
]
Michal Babacek commented on MODCLUSTER-443:
-------------------------------------------
O.K., I amended the test and IMHO this is no bug in proxy, but it's a wrong servlet
url mapping setup.
The following url works perfectly:
{{http://192.168.122.172:8080/tses;jsessionid=Qq7acr8AUL+212-o9bDcgtTJ.jboss-eap-6.4}}
Returning always the same session data:
{code}
<ul>
<li>Name: jj.test.com</li>
<li>Address: 192.168.122.172</li>
<li>JSESSIONID: Qq7acr8AUL+212-o9bDcgtTJ.jboss-eap-6.4</li>
</ul>
{code}
Provided one has this mapping (note url pattern):
{code}
<welcome-file-list>
<welcome-file>session.jsp</welcome-file>
</welcome-file-list>
<servlet>
<servlet-name>Hello</servlet-name>
<jsp-file>/session.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>Hello</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
{code}
What am I missing here?
mod_cluster doesn't recognize ; as a proper context delimiter
causing 404s on requests with URL jsessionids
-----------------------------------------------------------------------------------------------------------
Key: MODCLUSTER-443
URL:
https://issues.jboss.org/browse/MODCLUSTER-443
Project: mod_cluster
Issue Type: Bug
Components: Native (httpd modules)
Affects Versions: 1.2.9.Final, 1.3.1.Alpha2
Reporter: Aaron Ogburn
Assignee: Jean-Frederic Clere
This is similar to MODCLUSTER-328, but in regards to ; instead of ?.
mod_cluster does not recognize ; as a delimiter when checking the request context. Thus
with no trailing slash on index page requests, it treats ;jsessionid as part of the
request context and tries to check the balancer for a deployed context of
/helloworld;jsessionid=..., which doesn't exist and 404s. Adding the trailing slash,
mod_cluster can properly delimit this and then sees the context (so
/helloworld/;jsessionid=... works just fine).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)