X-Forwarded-For - Load Balancers

Load Balancers

Barracuda Load Balancer from Barracuda Networks supports user-defined headers such as X-Forwarded-For to insert the client IP address into a client request.

Citrix Systems' NetScaler supports user-defined fields such as X-Forwarded-For to insert the client IP address into a client request.

Cisco Ace Load Balancing Modules can also insert this field, usually implemented when the load balancer is configured to perform source NAT, to allow the load balancer to exist in a one-armed configuration, while providing a mechanism that the real servers can use to account for client source IP address. The reference mentions x-forward, however X-Forwarded-For can be substituted.

F5 Networks load balancers support X-Forwarded-For for one-armed and multi-armed configurations.

KEMP Technologies LoadMaster supports X-Forwarded-For for non-transparent load balancing in both one-armed configuration and multi-armed configurations.

Coyote Point Systems Equalizer supports X-Forwarded-For fields for load balancing in both one-armed configuration and multi-armed configurations.

OpenBSD relays can insert and/or alter this field.

Amazon's Elastic Load Balancing service supports this field.

LBL LoadBalancer supports X-Forwarded-For for one-armed and multi-armed configurations.

Radware AppDirector ADC, Alteon ADC, ADC-VX, and ADC-VA support inserting an X-Forwarded-For for header for traffic that is Source NAT towards servers, as well, as being capable of providing persistency of traffic based on the X-Forwarded-For header for distributing traffic from a proxied connection to multiple servers while preserving persistency to servers.