OneConnect and Persistence for HTTP App

Just to stick my nose in here, "OneConnect ensures that every L7 request is evaluated" is a pretty bad way to think about OneConnect.

 

 

There are two different issues, which admittedly behave differently, which OneConnect is involved in that are not obvious.

 

 

First is persistence. As you correctly state, without OneConnect, you're load-balancing connections, not requests, so the persistence cookie will only be evaluated once per connection. With OneConnect, you're load-balancing requests, so each request will will have its persistence cookie evaluated. See sol7964 for more on this.

 

 

Second is selecting a pool via iRules. With OneConnect, the default pool from the profile is started with for each request (again, since OneConnect load-balances requests, not connections). Without OneConnect, it isn't: the pool is only changed via iRule command. So if you have some giant switch statement or block of if {} tests, and you *don't* have a default clause which uses the pool command to explicitly choose the default pool, then OneConnect can cause a change in behavior.

 

 

But with or without OneConnect, every L7 request is always evaluated. iRule events will fire, HTTP profile settings will take effect, etc.