For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

JPMarine_163325's avatar
JPMarine_163325
Icon for Nimbostratus rankNimbostratus
Jun 19, 2018

Load Balancing through another brand load balancer

Hi,   We're working on an application that uses NGINX Load Balancers for their DB connections, but F5 (at the moment), for their web front end. The vendor apparently has convinced them to keep NGI...
application delivery
iRules
LTM
AceDawg1's avatar
AceDawg1
Icon for Nimbostratus rankNimbostratus
Jun 19, 2018

X-forwarded-for is typically implemented on any web based application: 99.9% of the time, this means web servers (Apache, IIS, Tomcat).

 

Doesn’t really matter the number or type of load balancers involved, each connection is a separate distinct session. So if the F5 was load balancing both the web and dB apps, chances are you’d have the same problems if the entire stack isn’t able to handle x-forwarded-for headers.

 

Have the nginx team create a vip for the web servers. Then use localhost entries for name resolution. Pretty certain they will have similar problems.

 

I’m a Linux guy so work primarily with MySQL and postgresql. That said, products like OneProxy help address the client IP address problem you’re facing.