Configuring Proxy address forwarding with WildFly

This tutorial discusses how to configure Proxy address forwarding with WildFly’s Web server (Undertow).

A common scenario in many architectures is to have WildFly server fronted by a reverse Proxy like Squid or Apache that maps the WildFly domain.

What happens is that, if you are using for example a navigation rule in your application such as:

<redirect />

Then WildFly redirects from HTTPS back to HTTP causing an error in the request.

One to solve the issue is to configure the proxy-address-forwarding on Undertow’s HTTP listener to enable the x-forwarded-host and similar headers and set a remote ip address and hostname.

Recent versions of WildFly, already ship with a Socket Binding for the https protocol:

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
        <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
        <socket-binding name="http" port="${jboss.http.port:8080}"/>
        <socket-binding name="https" port="${jboss.https.port:8443}"/>
        <socket-binding name="management-http" interface="management" port="${}"/>
        <socket-binding name="management-https" interface="management" port="${}"/>
        <socket-binding name="txn-recovery-environment" port="4712"/>
        <socket-binding name="txn-status-manager" port="4713"/>
        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="localhost" port="25"/>

If you don’t have it in your configuration, or you want to create another one using a different port, you can still do it as follows:


Next step will be adding on Undertow’s HTTP listener the attribute proxy-address-forwarding to true and as well set the redirect socket to be the socket binding from our configuration:


Here is Undertow’s updated configuration:

<subsystem xmlns="urn:jboss:domain:undertow:10.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other" statistics-enabled="${wildfly.undertow.statistics-enabled:${wildfly.statistics-enabled:false}}">
    <buffer-cache name="default"/>
    <server name="default-server">
        <http-listener name="default" socket-binding="http" redirect-socket="https" proxy-address-forwarding="true" enable-http2="true"/>
        <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>
        <host name="default-host" alias="localhost">
            <location name="/" handler="welcome-content"/>
            <http-invoker security-realm="ApplicationRealm"/>
    <servlet-container name="default">
        <file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>

Also, make sure the Reverse Proxy is sending in the Header (See for Squid:

X-Forwarded-Proto: https

Finally, another way to get around the problem is using the “secure” attribute in the http listener which causes requests that originate from this listener to be marked as secure, even if the request is not using HTTPS.


That’s all it takes to configure proxy-address-forwarding on Undertow’s HTTP listener