Re loadbalancing in a same pool without sending HTTP 302 redirect

I’m looking for a way to reloadbalance to different node in the same pool when BIG-IP receives 404 error from web server.

In this case, customer doesn’t want user to send HTTP 302 response.

It must be able to done since F5 released presentation document for the solution.

Any help would be much appreciated.

Hi hirox, this feature has not been released yet; it will be available on the next major release of BigIP. Could you please let me know where you found the incorrect documentation, I will make sure that it’s corrected.