When serving on 0.0.0.0 (for instance, launching standalone.sh with `-b 0.0.0.0`), some of the links in the management console don't work because they link to `0.0.0.0`.

More specifically:

• the context root link for a deployment points at `http://0.0.0.0:8080/myapp`
• The URL link for the server in the "Runtime" tab is `http://0.0.0.0:8080`

The use of `0.0.0.0` is convenient as it's a good default for deployments on remote servers, but it would be nice if these management console links worked out of the box.

A proposed solution would be for the management console to infer the hostname from the "Host" http header when the configured host is 0.0.0.0.

Of course, the impact of this behavior is minimal, and workarounds are straightforward:

• Specifying a specific interface (if feasible) in the wildfly startup/config
• Just deal with it (manually change the URL in the browser)