[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-3042: ---------------------------------- Fix Version/s: Open To Community (was: 7.1.0.Final) Assignee: (was: Darran Lofthouse) I am postponing this issue for the moment. The behaviour of the /console context on port 8080 is supposed to be a simple redirect so that out of the box users that connect to 8080 (Most likely out of habit as that is where previous AS management was performed) can be redirected to the admin console on it's dedicated port. This re-direct however is not intended to be covering every network topology that can be imagined, once a server is moving beyond the initial set up these welcome pages should be switched off and administrators connect directly to the port hosting the admin console. For this issue one address has been bound to an IPV6 format of the loopback address and the other address to the IPV4 equivalent - really once an administrator has reached this point they are beyond trying to work out where the admin console is accessible from - also we need to be very careful regarding the information returned from port 8080 as we should not be revealing information about the internal network over this connection as we can not actually verify the remote client has access - this is why the check is limited to verifying the same network interface is being used and relying on a best efforts redirect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira