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

vf-mt_243104's avatar
vf-mt_243104
Icon for Altocumulus rankAltocumulus
Nov 07, 2017

Forwarding Traffic to URL rather than Pool

Hi,   In our current implementation of LTM, we create multiple virtual servers with each having it's own Policy. In the Policy, rules define domain based or URI path based requests, and forward to...
application delivery
BIG-IP
LTM
Henrik_S_142222's avatar
Henrik_S_142222
Icon for Altostratus rankAltostratus
Nov 07, 2017

The whole concept of LTM is to either respond directly or to forward requests to pool member. As long as the service you want to forward requests to is publicly available, why not just make the LTM respond with a normal HTTP::redirect ? If not you could probably leverage SNAT and create a pool with FQDN pool member. You can configure the LTM to auto populate and you can choose the interval that the LTM re-queries DNS. By default auto populate is on and re-checks once an hour. If an IP is not returned that was originally it will be removed and subsequently, if a new IP is returned it will be added.