On Mon, 2009-01-26 at 17:28 +0100, jean-frederic clere wrote:
Paul Ferraro wrote:
> On Mon, 2009-01-26 at 16:48 +0100, jean-frederic clere wrote:
>> Paul Ferraro wrote:
>>> 1.0.0.Beta3 adds a new excludedContexts configuration property that
>>> defines a comma delimited list of web contexts that should *not*
>>> auto-register with httpd. Does anyone have any suggestions/comments
>>> about which contexts to disable by default? Currently, this property
>>> defaults to:
>>>
>>> <property
name="excludedContexts">ROOT,invoker,jbossws,jmx-console,juddi,web-console</property>
>>>
>>> i.e. all contexts deployed by default in the JBoss AS all profile.
>>>
>>> As I think about this more, I think we should use a system property for
>>> this instead - and perhaps enable the ROOT context by default?
>> Enable ROOT context by default is probably not a good idea. every
>> requests will go to JBoss and probably will return 404.
>>
> Why would there be any requests for these webapps via httpd at all?
ROOT corresponds to / so everything will be rooted to JBoss by default.
I am not sure that is a good default.
I realize this, *and* I'm saying that this is the prime use case - that
the context most users will want load balanced is the root context. No
requests for any of the other contexts would ever be made from httpd -
if somebody did, a 404 is entirely appropriate.
I'll keep ROOT excluded until you're thoroughly convinced... ;)
Cheers
Jean-Frederic