iRule TCL Error and Fallback Host

Hi,

Just another finding that surprised me a bit :slight_smile:

Scenario:

  • HTTP profile with Fallback Host set (Fallback on Error Codes can be empty or contain codes)
  • Single member pool
  • iRule causing TCL error

I was under impression that Fallback Host is used under two conditions:

  • Member returned one of codes defined in Fallback on Error Codes
  • There is no active member left in the pool

It turns out that Fallback Host is as well used when iRule TCL Error is generated - instead of sending RST to client. Then BIG-IP sends FIN-ACK to client to close connection.

Piotr

From K6510: BIG-IP system fallback host behavior when a host is down:

When a Fallback Host is defined, and the connection attempt to the selected load balancing target has failed by the time the BIG-IP LTM system is ready to send the request, the BIG-IP LTM system sends the specified HTTP redirect in the following situations:

   - A pool member has not been chosen (the system failed to select a pool or a pool member, or no pool members were available)
   - A pool member is unreachable (when no route to the target exists)
   - A pool member is unresponsive (resets a connection request)
   - A pool member closes an established connection before the request is sent

.

Please read answer posted by F5 in this thread

“Anything that raises an abort above the HTTP filter in the chain will trigger a HTTP fallback. This includes things like errors in iRules, Out of Memory situations, misconfiguration, and of course the proxy failing to connect”