Original X-Forwarded-For Header Not Forwarded Through LoadBalancer in Red Hat JBoss EAP

Issue

• We've set up an EAP balancer or proxy with another proxy in front of it. The EAP proxy receives the original client X-Forwarded-For ip address, but it overrides it in its proxied reqeusts so our destination servers are not receiving the original client ip in the X-Forwarded-For.