Forum Discussion
Nicolas,
Again. I much appreciate the effort you have put into this.
Here is what I have done based on your suggestions.
I did open up the developer tools in the browser. Private browser setting is not available on any of our browsers in our work environment. However. I believe I could see all the info you described.
First, I set the cookie profile for this virtual server to not do encryption in order to check/verify the value setting. I then went back to the working environment (no local traffic policy, irule only doing header insert, landing on round robin backend server). I could view the cookie as you described. It is set in the response and then the next time, it is sent in the request. I verified that this is the value that I use when I apply the local traffic policy. All that matches and looks good (name, values)
Then, I implemented the policy and the irule with the catch LB. Again I could see the correct cookie being set and then sent in the subsequent request. However, there is still the same issue with the load balancer selecting a backend server in the same round robin fashion as before.
I can send you screen shots, but it all looked good and matched what you showed.
This is a production application that is on a time line. Although the idea of having one virtual server with a user being able to add a uri to select a specific backend would have been the preferred solution, this does not appear to be doable on the F5 LTM, possibly because of using an access policy? We know that we can get this to work with having one virtual server per backend server. Although this means 10+ virtual servers, a solution we really didn't want, a working solution is better than a non-working solution, especially because this would have been in place weeks ago.
If you have any thoughts on how this could be accomplished without having one virtual server per backend server, that would be appreciated. I probably haven't considered other possible (working) solutions.