Possible performance issue with iRule?

And that's the solution ID I couldnt find this morning, thanks Aaron. The problem occurs on LTM as well. The solution ID is not entirely correct, you don't have to be using one connect. Essentially HTTP classes are sticky so subsequent requests in the same TCP connection *regardless of URI* go to the same pool which is not what you would expect. The solution is to always implement a catch all HTTP class at the end to make sure non matching requests are sent to the correct pool.