Forum Discussion
Ian_Stewart_390
Nimbostratus
Oct 14, 2005iRules, URL Routing and Cookie Persistance
Hi Everyone,
We have a BigIP 1500, configured with several virtual servers and pools. We use an iRule to make routing decisions to direct traffic to the correct pool based on request URL, si...
drteeth_127330
Oct 14, 2005Historic F5 Account
Okay okay. Hold on a sec. There should be no problems with SSL termination and cookie persistence. In fact, I don't think there are any problems here at all.
You have configured cookie insert persistence with source address persistence as fallback. First, cookie insert persistence does not create a persistence record. The persistence information is stored in the cookie itself.
When a client connects to BIG-IP and makes a request, BIG-IP will look for a session persistence cookie. If one is found, it will direct the request to the same server as was used for previous connections. If no persistence cookie is found, it will fall back to source address persistence. This means that it will consult the session persistence table for an entry matching the source IP address. For the first request from a new client, no entry will be present, so BIG-IP will create one. This is why you see the SOURCE ADDRESS AFFINITY records.
As for the load balancing test, I would expect every request from the same source address to be directed to the same server. That's source address persistence!
I hope this clears things up...
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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