[
https://issues.jboss.org/browse/MODCLUSTER-364?page=com.atlassian.jira.pl...
]
Michal Babacek moved JBQA-7899 to MODCLUSTER-364:
-------------------------------------------------
Project: mod_cluster (was: JBoss QA)
Key: MODCLUSTER-364 (was: JBQA-7899)
Issue Type: Bug (was: Task)
Workflow: GIT Pull Request workflow (was: classic default workflow)
mod_cluster and mod_proxy : keeping session
-------------------------------------------
Key: MODCLUSTER-364
URL:
https://issues.jboss.org/browse/MODCLUSTER-364
Project: mod_cluster
Issue Type: Bug
Reporter: Michal Babacek
Assignee: Michal Babacek
Labels: mod_cluster
Why this config:
{noformat}
ProxyPassMatch ^/app/static/ !
ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
ProxyPass / !
ProxyPassReverse /app balancer://qacluster
ProxyPassReverseCookieDomain / /app/
ProxyPassReverseCookiePath / /app/
ProxyPreserveHost on
{noformat}
does not keep the same session? I keep getting new sessions while hitting F5 with
{{http://server:6666/app/clusterbench/requestinfo/}}
*TODO:* Investigate whether it is a configuration error or mod_clutser's
incompatibility.
According to this [blog
post|http://www.brandonchecketts.com/archives/use-proxypassreversecookied...],
it should be trivial :-(
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira