Forum Discussion
m1978_295079
Jun 16, 2017Nimbostratus
Configuring Sticky session or Destination address affinity persistence
I need to configure sticky session in two pool members out of four. So the current set up is as below
Client ----https---F5 (offloading)--http-- Four Pool members
Now out of four pool membe...
IheartF5_45022
Jun 16, 2017Nacreous
That requirement doesn't make sense to me as a standalone requirement. It only makes sense if there is an additional requirement - for instance some paths or file types get sent to the sticky server and some don't. Let's say your requirement is for js/css and images to be sent to the non-sticky servers and for all other requests to be sent to the dynamic servers.
- Create 2 pools pl_dynamic and pl_static.
- Create a virtual server vs_web with http, oneconnect and cookie insert (persistence) profiles
- Make pl_dynamic the default pool on vs_web
- Create the iRule ir_pool_select below and attach to vs_web
when HTTP_REQUEST {
switch -glob -- [HTTP::uri] {
"*.js" -
"*.css" -
"*.png" {
# Send to pl_static
pool pl_static
# Turn persistence off for the static pool
persist none
return
}
}
}
Pulling my hair out - why can't I make this code formatting work?????
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects