[
https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-397:
------------------------------------------------
In fact may be we should have a flag at the VirtualHost level that bypasses mod_cluster
logic and just uses the ProxyPass/ProxyPassMatch logic...
Just to make sure I get it right the customers want to get a 503 and actually they get a
404 is that correct?
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