Can anyone reproduce this issue I'm seeing on upstream master:

Given a JSF page with a link

{code}
<h:commandLink action="test2?faces-redirect=true">link</h:commandLink>
{code}

and the app running on https://localhost/Test/faces/test.xhtml, attempts to load

https://localhost:80/Test/faces/test2.xhtml

are made (failing, of course). The port is 80 even if the http connector is 8080 (it's 80 even if the http connector is removed altogether)

My connectors are like

{code}
        <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host">
            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
            <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https">
                <ssl name="ssl" key-alias="jbossas7" password="jbossas7" certificate-key-file="c:/users/karlsnic/jbossas7.keystore"/>
            </connector>
            <virtual-server name="default-host" enable-welcome-root="true">
                <alias name="localhost"/>
                <alias name="example.com"/>
            </virtual-server>
        </subsystem>
{code}

and the bindings like

{codel}
        <socket-binding name="http" port="8080"/>
        <socket-binding name="https" port="443"/>
{code}

If I change the https port away from 443 to e.g. 8443 it works since apparently it no longer has to try to determine to port itself. Most browsers drop the 443 and 80 from the urls

Attached is a sample application with two jsf pages