[ https://issues.redhat.com/browse/MODCLUSTER-703?page=com.atlassian.jira.p... ]
ASM SDCO commented on MODCLUSTER-703:
-------------------------------------
Hello,
Any news ?
Thibault
> Handle multiple JSESSIONID with overlapping domains or paths
> -------------------------------------------------------------
>
> Key: MODCLUSTER-703
> URL: https://issues.redhat.com/browse/MODCLUSTER-703
> Project: mod_cluster
> Issue Type: Feature Request
> Components: Native (httpd modules)
> Affects Versions: 1.3.8.Final
> Environment: Apache 2.4.x
> jbcs-httpd24-mod_cluster-native-1.3.8-3.Final_redhat_2.jbcs.el7.x86_64
> Reporter: Frederic CORNUAU
> Assignee: Radoslav Husar
> Priority: Critical
> Labels: JSESSIONID, mod_cluster
>
> We currently migrate our Apache LB mechanism from _mod_jk_ to _mod_proxy_cluster_ and we face an issue when multiple JSESSIONID (with overlapping domains or paths) are being received.
> mod_jk supports multiple JSESSIONID cookies and is able to select the most suitable one based on the jvmRoute (see https://bz.apache.org/bugzilla/show_bug.cgi?id=44116 and https://github.com/apache/tomcat-connectors/blob/trunk/native/common/jk_l...).
> On the other hand, _mod_proxy_cluster_ uses only the first JSESSIONID received in the "Cookie" HTTP request header (see https://github.com/modcluster/mod_cluster/blob/1.3.8.Final/native/mod_pro...).
> Is-it possible to update _mod_proxy_cluster_ implementation to handle multiple JSESSIONID cookies?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)