Using HTTPClasses vs. iRules path & domain selection
Obviously HTTPClasses are very easy to configure and dummy proof where when we get into iRules, it can always get interesting (we are a large provider where lots of engineers touch lot of different LTMs)
From what I gather, LTM will only capture new flows when HTTPclasses are used so if there are multiple selections are done via HTTPClass, like /appA goes to POOL-AppA, /appB goes to POOL-AppB, and if persistence is enabled for the VS (e.g. cookie insert), when a user switches from appA to AppB things do not function.
Some F5 engineers tell us that HTTPClass should only be used for ASM purposes to filter ASM related traffic (bind ASM policy etc) and some of them tell us HTTPclasses are safe to use for any kind of traffic (with or without persistence). Currently we try to do everything with iRules, but I just want to see what your thoughts/experiences may be.
Regards, Haluk