irule to do smarter cookie persistance

Let me confirm the scenario. Do you have a two tiered web app with a web tier and app tier? Do both sets of requests (from client to web and web to app) need to be persisted to the same servers? If so, you could potentially use an iRule on the web to app virtual server which persists based on the client's web virtual server persistence cookie. You could use 'persist uie $web_vs_cookie_value' to do this in HTTP_REQUEST. With this or any other layer 7 per HTTP-request persistence method, you'll need a OneConnect profile for each virtual server.

 

 

Any solution you come up with for LTM is going to require testing to confirm it will work. So I'm not sure the lack of appetite for a research project is going to be workable.

 

 

How would a custom cookie which has the server name specified be different than the default cookie insert persistence? Yes, you could rewrite the cookie insert persistence functionality in an iRule. But why would you?

 

 

Aaron