Forum Discussion

Paul_Slosberg_8's avatar
Paul_Slosberg_8
Historic F5 Account
Feb 08, 2008

Cookie persistence HTTP HTTPS new twist

Greetins,

I have read Deb's article on how to archive this without iRules help. I have one twist that I need help with. I will have a 2 virtuals listening on 80 and 443 and they will share a pool (wildcard members) and a cookie persistence profile. The HTTPS virtual will have a client and a server side SSL profile. (Requirement to re-encrypt to the back-end).

This is all very easy.. Here is the twist the servers will be listening on 8080 and 8443. They will not change this. So I would need a way to do the port translation via an iRule to maintain the persistence across the services. Or I can use source base persistence and match across services with the built in port translation capabilities of LTM. But I would rather not do this.

Any help would be groovy.


 when CLIENT_ACCEPTED {
 set LB port based on requested port
switch [TCP::local_port] {
443 {set port 8443}
80 {set port 8080}
}

  • you don't need an iRule to do this... it is in fact automagic.

     

     

    the serverside connection is established to the ip and port of the selected pool member....

     

     

    so if you define the ssl pool with members like:

     

    192.168.1.1:8443

     

     

    It will just work.