Setup: One master and one agent in a sub cluster. listen_port on master: 300 listen_port on agent: 301 Outcome: When trying to login through web access the authentication works but the web access on master tries to redirect to the agent using its own listen_port instead of the one defined in webaccess.hconf on the agent. Since nothing is running on port 300 on the agent the connection is refused. Expected outcome: Successful redirect to agent Use case / Scenarios: Probably never. But its not obvious that this setup will not work and it is not documented, this could lead to confusion.
The use case here was that the customer only has a single IP and wants to make a cluster available by using different ports. We already have bug 3003 for this, although it focuses on the native client rather than Web Access.
https://community.thinlinc.com/t/is-there-a-host-aliases-like-workaround-for-the-browser-client/372
