[
https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl...
]
Aaron Ogburn commented on MODCLUSTER-397:
-----------------------------------------
Thanks for the response, JF. I think a lot of users would expect this to work and
we've gotten a couple of support side complaints now about it. They'd prefer
using this to a PT rewrite (especially on the attached case). It looks like we only call
get_route_balancer and check the route in proxy_cluster_trans against the originally
requested uri (/). I was able make this work by also calling get_route_balancer in
proxy_cluster_canon to be able to check the stickysession against the end proxy
destination uri (/foo). Would we be able to implement something like this to be able to
handle this use case?
StickySessions don't work for ProxyPass from unenabled context
--------------------------------------------------------------
Key: MODCLUSTER-397
URL:
https://issues.jboss.org/browse/MODCLUSTER-397
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.2.8.Final
Reporter: Aaron Ogburn
Assignee: Jean-Frederic Clere
Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to
an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP.
Then try to ProxyPass / to /foo/ on httpd:
CreateBalancers 1
...
ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On
--
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