[
https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira...
]
Radoslav Husar commented on MODCLUSTER-123:
-------------------------------------------
Hi again, so JF, do we make this into another Jira?
On 01/13/2010 11:45 AM, jean-frederic clere wrote:
Once / is deployed that means you want all requests to be forwarded to
jboss, I wasn't think the other may not want a request starting with
/load-demo/ going to the ROOT application. May be that needs to be
switchable.
(Even though the concern is also that if /load-demo is DISABLED but / is ENABLED loaddemo
requests will *still* go to the disabled /load-demo, but I cant say whether this is a
real-life thing for people to be using.)
Disabling contexts does not work
--------------------------------
Key: MODCLUSTER-123
URL:
https://jira.jboss.org/jira/browse/MODCLUSTER-123
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Environment: RHEL 5.4
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
Priority: Minor
Disabling contexts does not work and it keeps connecting on disabled contexts on the
specified node (neither does 'disable all contexts' option).
Note that in mod_cluster-manager it displays correctly that its disabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira