Forum Discussion
Jason_L_40779
Nimbostratus
NimbostratusPersistence/Proxy
I have an internal app using an http frontend that I am load balancing for 4 web servers. Last spring they upgraded the version of code on the clients and the client lost the ability to use an http cookie. so I could no longer use a cookie for persistence. I switched to a source address persistence profile which has worked very well. They now want to allow remote clients to talk to this app behind a proxy to my VIP. My thought is the clients are all going to appear to the BipIP as the same source address from the proxy. Therefore, the source address persistence will direct all remote clients to the same web server. Anyone have any experience working behind a different proxy and what other methods of persistence could be used...
I know the cookie persistence is not going to work with this application.
Thanks
HamishCirrocumulus
OK. Sounds like it's HTTP at least... And I'm assuming here you have access to the stream (As you used to do cookies), so there's no problems there. The BigIP can persist on other information in the headers... All you need to do is to find out which headers the application itself is using to track the individual users and persist on that...
You'll either have to tcpdump the traffic and work on decoding it, or speak to the developers who wrote the frontend/backend software and ask them.
Then create an iRule that will decode this information and select a persistence entry. Match that up with a Universal persistence profile and you should be away.
H
Jason_L_40779beautiful, I was thinking irule also but wasn't sure what to look for. I really appreciate the information. I'll post back and let you know how it goes.