Description of problem: 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). Version-Release number of selected component (if applicable): 1.2.10.Alpha How reproducible: Always Steps to Reproduce: 1. Deploy /helloworld in a mod_cluster set up 2. Request "/helloworld;jsessionid=bla" through httpd Actual results: A 404 is returned Expected results: The request is served Additional info:
PR: https://github.com/modcluster/mod_cluster/pull/132
Please, see my comment on the linked JIRA: https://issues.jboss.org/browse/MODCLUSTER-443?focusedCommentId=13020708&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13020708
Needs an upgrade to mod_cluster 1.2.11.Final
Escalating Severity due to the pending customer case.
Switching to MODIFIED, the patch has been merged.
mod_cluster component hasn't been upgraded to 1.2.11.Final. This fix ain't present in EAP 6.4.0.ER1.
Fixed by 1.2.11 upgrade
Verified with EAP 6.4.0.ER2