Using modcluster filter with local content creates loop

We have two WildFly-servers (ServerA, ServerB) with mod_cluster support:

        <subsystem xmlns="urn:jboss:domain:undertow:3.0">
            <buffer-cache name="default"/>
            <server name="default-server">
                <ajp-listener name="ajp" socket-binding="ajp"/>
                <http-listener name="default" redirect-socket="https" socket-binding="http"/>
                <host name="default-host" alias="127.0.0.1">
                    <location name="/" handler="welcome-content"/>
                    <filter-ref name="server-header"/>
                    <filter-ref name="x-powered-by-header"/>
                    <filter-ref name="modcluster"/>
                </host>

In addition we deploy an application on both servers with a context e.g. /myapp

When we call /myapp on ServerA (or ServerB), we won't get a response. The reason is, that the filter modcluster on ServerA sees that context /myapp is available on ServerB and sends the request to ServerB. Then modcluster on ServerB sends the request back to ServerA.

If the context (/myapp) is available on the local server, the modcluster filter should not send the request to another server, but let it handle locally.

This setup might not be intended originally, however in https://developer.jboss.org/thread/267281 there is a description why this might be an interesting configuration. Links to complete setup-scripts for an example configuration are provided as well.