HTTP::URI redirect to another Pool

If the pool members have a route back to the client through LTM, you can avoid using SNAT and LTM won't translate the source IP to its own address on serverside connections. If the pool members don't have LTM as their default gateway or the clients are on the same subnet as the pool members, you'll need to use SNAT. The simplest way to enable SNAT is to set SNAT to automap on the virtual server.

 

 

For HTTP or LTM decrypted HTTPS, you can insert a custom X-Forwarded-For header which the web application can read. SeeSOL4816 for details on this:

 

 

SOL4816: Using the X-Forwarded-For HTTP header to preserve the original client IP address for traffic translated by a SNAT

 

https://support.f5.com/kb/en-us/solutions/public/4000/800/sol4816.html

 

 

Aaron