[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Jean-Frederic Clere edited comment on MODCLUSTER-123 at 1/8/10 10:31 AM: ------------------------------------------------------------------------- I can't reproduce this one. Are you sure you are testing that correctly? DISABLE means it won't accept requests without sessionid, could it be that you send a sessionid somehow? was (Author: jfrederic.clere(a)jboss.com): I can't reproduce this one. Are you sure you are test that correctly? DISABLE means it won't accept requests without sessionid, could it be that you send a sessionid somehow? -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Radoslav Husar commented on MODCLUSTER-123: ------------------------------------------- So we tried again. How to reproduce: launch 2 nodes disable given context on both issue new request (with no cookies) voila, answer from one node with 200 return code -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] 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? -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Jean-Frederic Clere updated MODCLUSTER-123: ------------------------------------------- Priority: Minor (was: Major) -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Jean-Frederic Clere commented on MODCLUSTER-123: ------------------------------------------------ Yep another JIRA is OK. I have started to work on the idea in 1.1.x I am still thinking that if a user deploys / it is because it wants to see all requests going to ROOT (for example to have the 404 page for Tomcat instead the httpd one). -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Jean-Frederic Clere updated MODCLUSTER-123: ------------------------------------------- Fix Version/s: 1.1.0.CR1 -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Laura Bailey commented on MODCLUSTER-123: ----------------------------------------- Documented as a known issue in the EAP 5.0 release notes. Please verify that the following is appropriate: "If the root context ("/") is deployed and enabled, other contexts cannot be disabled. It is also impossible to specify that other contexts not be forwarded to the root context." -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Jean-Frederic Clere reassigned MODCLUSTER-123: ---------------------------------------------- Assignee: Laura Bailey (was: Jean-Frederic Clere) Just doc -- 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

[ https://jira.jboss.org/jira/browse/MODCLUSTER-123?page=com.atlassian.jira... ] Jean-Frederic Clere closed MODCLUSTER-123. ------------------------------------------ Resolution: Done Documented in release notices. -- 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