[
https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl...
]
Michal Babacek commented on MODCLUSTER-443:
-------------------------------------------
Well, the problem was located exactly between the chair and my keyboard. I'm sorry.
{quote}
http://192.168.122.172:8080/tses;jsessionid=Qq7acr8AUL+212-o9bDcgtTJ.jbos...
{quote}
The test executed with _worker's_ port, not the balancer's one. With this fixed,
indeed, now it doesn't work:
Works with EAP worker:
{code}
curl
'http://192.168.122.172:8080/tses;jsessionid=HfYUfMkbXbaeKZ+SpgQbVqd5.jboss-eap-6.4'
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<title>Session Test</title>
</head>
<body>
<h3>Server info</h3>
<ul>
<li>Jsessionid: HfYUfMkbXbaeKZ+SpgQbVqd5.jboss-eap-6.4</li>
</ul>
</body>
</html>
{code}
Doesn't work via balancer:
{code}
curl
'http://192.168.122.172:8847/tses;jsessionid=HfYUfMkbXbaeKZ+SpgQbVqd5.jboss-eap-6.4'
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /tses;jsessionid=HfYUfMkbXbaeKZ+SpgQbVqd5.jboss-eap-6.4 was not
found on this server.</p>
<hr>
<address>Apache/2.2.26 (Red Hat Enterprise Web Server) Server at 192.168.122.172
Port 8847</address>
</body></html>
{code}
The test is amended and added to the continuous QA cycle now.
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)