If-Then-Else within a Switch

Hi Aaron. Thanks again for taking the time to look at this. The rule doesn't appear to be doing that. I thought it was odd as well but it appears as if it's either only working for pool_2 (or it isn't working at all). It's tough for me to tell from a tcpdump what is a multiplexed connection versus one that is persistent/keep-alive and there is no pattern to this particular end-user's request other that their requests are spaced relatively far apart.

 

 

I have an updated rule I'm putting into a staging environment to make sure there is no adverse impact that moves the reuse disable down into the if sections, to see if that helps.