]
Radoslav Husar updated MODCLUSTER-477:
--------------------------------------
Affects Version/s: 1.4.0.Final
Broken design: session cookie name should be specified on the Context
level instead of the Engine level
-------------------------------------------------------------------------------------------------------
Key: MODCLUSTER-477
URL:
https://issues.jboss.org/browse/MODCLUSTER-477
Project: mod_cluster
Issue Type: Bug
Components: Core & Container Integration (Java), Documentation &
Demos, Native (httpd modules)
Affects Versions: 1.0.10, 1.1.3.Final, 1.2.11.Final, 1.3.1.Final, 1.4.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Critical
Fix For: 2.0.0.Alpha1
In web.xml [2], user is allowed to configure cookie name per context. However, in MCMP
[1] this configuration is only propagated on the CONFIG -
org.jboss.modcluster.container.Engine level.
This essentially means that user configuring a cookie name different from the default /
or default host configuration will have broken session stickiness.
[2]
https://developer.jboss.org/wiki/Mod-ClusterManagementProtocol
[1]
{code:xml}
<xsd:element name="name"
type="javaee:cookie-nameType"
minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The name that will be assigned to any session tracking
cookies created by this web application.
The default is JSESSIONID
</xsd:documentation>
</xsd:annotation>
</xsd:element>
{code}