F5 LTM Sticky Sessions between 80/443
I'm new to F5. We bought 2 1600s, but couldn't afford training so I'm winging it. I used to use another load balancer product and am having to figure this out as I go. I need some major help with what may be a simple problem.
I've got 3 portal servers that have authentication pages on them. The portal is poorly written and does a number of redirects through the login process. You start on port 80...go to 443 for the login page...then get redirected back to 80 after a successful login. I created 2 virtual servers that point at 80 & 443 and set cookie persistance on each.
The problem is, since they're separate virtual servers a client can pull server1 on the first 80 request, server2 for the 443 auth, and server3 after they successfully login. It results in the cookie stating that the user has authenticated, but the final server's session data doesn't match the one they posted their credentials with.
What I want is a way to stick all 80/443 connection to that virtual hostname to one physical server per cleint connection...thus keeping everything working and being as transparent to both the end user/server as possible. Not sure if this would be an iRule or creating a new persistance profile. I've never done either, so I don't know where to start. Any help would be most appreciated.