[
https://issues.jboss.org/browse/MODCLUSTER-587?page=com.atlassian.jira.pl...
]
Paul Ferraro commented on MODCLUSTER-587:
-----------------------------------------
The root location would only need to be removed if a web application wants to use the root
context. This is true whether mod_cluster is used or not.
The purpose of the "welcome" content is to verify that web requests work.
Exposing the "welcome" content to the load balancer does the same, but for load
balanced web requests.
So, in summary, I disagree with the premise of this jira.
Docs: Undertow hosts root location is exposed(by default) to
mod_cluster load balancer
--------------------------------------------------------------------------------------
Key: MODCLUSTER-587
URL:
https://issues.jboss.org/browse/MODCLUSTER-587
Project: mod_cluster
Issue Type: Bug
Components: Documentation & Demos
Reporter: Bogdan Sikora
Assignee: Michal Karm Babacek
Undertow can be configured to serve static content per host via the location resource.
This location resource is exposed to the mod_cluster balancer.
{noformat}
"context" => {
"/custom_location" => {
"requests" => 0,
"status" => "enabled"
},
{noformat}
However, all EAP standalone profiles have enabled root location by default. This root
location is then exposed to the balancer( Application root "/" is registered).
{noformat}
"context" => {
"/" => {
"requests" => 0,
"status" => "enabled"
},
{noformat}
Root application matches with any application call and therefore mod_cluster balancer is
unable to correctly route requests.
To make mod_cluster work, one must delete root location from worker nodes.
{noformat}
/subsystem=undertow/server=default-server/host=default-host/location=\/:remove()
{noformat}
or excluding context ROOT
{noformat}
/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=excluded-contexts,value="ROOT")
{noformat}
*_+Proposal:+_*
Exclude ROOT context by default
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)