For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Ian_Stewart_390's avatar
Ian_Stewart_390
Icon for Nimbostratus rankNimbostratus
Oct 14, 2005

iRules, 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...
application delivery
dev
devops
iRules
Ian_Stewart_390's avatar
Ian_Stewart_390
Icon for Nimbostratus rankNimbostratus
Oct 14, 2005
To test your idea, I put a log line just after the set defpool command.

 

 

My local traffic log filled with lines like:

 

 

Rule URL_Routing : Default pool is: webnode3_pool

 

 

So it would seem that the default pool was being set correctly.

 

 

I was thinking:

 

 

What I want to happen is that should someone request http://www.mywebsite.com/cpm/, I want them to be processed by this rule, and then persisted to whatever node in the CPM_Pool that they get load balanced on to. We want our website to appear as one site, even though different URL paths are serviced by different web applications, running on different pools.

 

 

The way this is written though, I'm wondering if it's possible that for each request, this iRule runs again, and they have the danger of being re-load balanced. If they were, the site would be quite broken though, we'd know right away. Perhaps the F5 detected this and is using Source Address Affinity? Does any of that sound reasonable? If so, what alternative solution might you suggest?

 

 

-Ian