Radoslav Husar updated MODCLUSTER-531:
Affects Version/s: 1.3.0.Final
Issue Type: Enhancement
Components: Core & Container Integration (Java), Documentation &
Demos, Native (httpd modules)
Affects Versions: 1.2.0.Final, 1.3.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 2.0.0.Alpha1
I am proposing we abandon automagic as much as possible.
The main idea for automagic is to make deployment simple and easy to migrate/transfer and
provide great user experience out of box. Unfortunately, this IMHO often backfires quite
significantly resulting in configurations that are:
# insecure (listening on all interfaces, allow from all, default security key
# difficult to debug (not clear what is the actual configuration)
# unstable installations (seemingly unrelated aspects like adding an interface or
connector break the config)
There are several areas where automagic happens.
h5. Advertised address of the proxy
There were multiple bugs in the past, where 0.0.0.0 would be sent in the advertise
mesages, now if its not explcit in the VirtualHost or passed in to ServerAdvertise, it
automagically picks a non-local interface. Such configurations should be disallowed.
h5. Advertise interfaces
The interfaces are not explicit and advertise messages could be sent/received on more
interfaces (related MODCLUSTER-487). This is also problematic when trying to move to
DatagramChannel interface, which requires interfaces to be defined explicitly
(MODCLUSTER-502). We can require this explicitly.
h5. Connector address
If bound to any-address, the address is inferred from the proxy connection as the local
address. This is solved in the default WildFly configuration as its explicitly bound to a
h5. Connector selection
This is solved in WildFly where selection is explicit. In tomcat this causes problems
like MODCLUSTER-457 when WS requires http yet ajp is automatically selected by default. We
can make this explicit.
h5. Route generation
Remove setJvmRoute from the SPI.