[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-123) Disabling contexts does not work

[Radoslav Husar (JIRA)]

    [ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12503818#action_12503818 ] 

Radoslav Husar commented on MODCLUSTER-123:
-------------------------------------------

So I will move the discussion here. So it looks like we had ROOT context deployed, which i thought we didnt, so let me update.  My concerns are still (even though deploying ROOT context does not seem production-like setup).

* there is no mention in the documentation

* if you have contexts "/" and "/test" and you disable "/test", but "/" is still enabled, the requests will be still routed to /test app. However if you have "/" disabled and "/test" enabled, requests will be still routed to "/test". So you need to have both disabled to disable that /test context. So this is quite confusing and it could follow some order of denying and allowing.

So i guess for the sake of EAP we leave this as documentation fix and maybe a small feature request?

> 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
>
> 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