Forum Discussion
On the cookie & source_addr persistence, I have argued and even pointed out where in the F5 deployment guide that they keep forwarding to me, that it says in big red box to not use source addr persistence. But, they keep wanting it put back in as the fall back.
It occurred to me later that maybe I was trying to do the member selection override in the wrong event.
I had also thought about separate pool...but worried that it'll lead to confusion for the application administrators (who have operator access to the F5) when they want to force a member down in preparation for maintenance. But, I thnk that's what I'll try.
Though with a bit of change, since http profile has a redirect on failure which they don't want happening for this exception.