Reselect on Service Down - HTTP Web Apps

Hi All,

 

Historically my company has ALWAYS used the option of "Reselect" as our preferred default option for our external and internal web apps. Recently we logged a support ticket with F5 and they highlighted this Solution article ( https://support.f5.com/kb/en-us/solutions/public/15000/000/sol15095.html ) and it explicitly states that "Reselect" is useful only if the pool is only appropriate in the below circumstances:

 

• Virtual servers with address and port translation disabled Note: This is the default for FastL4 type virtual servers, such as network or wildcard forwarding.
• Transparent pool members, such as firewalls, routers, proxy servers, and cache servers Note: Transparent devices can forward packets to destinations without regard for the state of the connection.
• UDP virtual servers

So obviously all our HTTP pools are now misconfigured, but I am wondering if anyone knows what would occur with HTTP applications if we continue with "Reselect" as our default ??

 

What would be the best default option for HTTP apps then ?

 

I assume "Reject" would be the best as the client would get a TCP reset back. To be honest, surely there has to be a better way, if your not dealing with savy users that know the F5 button on the keyboard are they going to use it ?

 

None is not really an option, we use cookie based persistence on a lot of apps and if a server is down for any reason that would be a disaster.

 

That leaves Drop, which gives NO feedback to the users.