It would be ideal if Spring Framework provided a transparent way to support x-forwarded headers similar to Tomcat's RemoteIpFilter. This would provide an application container independent way of supporting x-forwarded headers.
Admittedly, #14743 added support for this. However, this is not ideal because the framework and users must leverage the newly added APIs explicitly. Furthermore, always interpreting the request using x-forwarded- allows forging the address so users should really opt in for this (i.e. by adding a Filter).