Forum Discussion
Paul_Slosberg_8
Feb 08, 2008Historic F5 Account
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}
}
- David_Remington
Employee
you don't need an iRule to do this... it is in fact automagic.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects