I noticed that the undertow configuration supports the "proxy-address-forwarding" for the <http-listener>. This causes it to interpret X-Forwarded-Proto and X-Forwarded-For headers if WildFly is behind a reverse proxy (nginx in my case).
I need to use SSL between the reverse proxy and WildFly servers (for extra security).
Currently the <https-listener> (note the 's') does not support "proxy-address-forwarding".
Could this be added? Shall I raise a Jira? Or is there another way of achieving the same result?