Bind HTTP & HTTPS Traffic To Same Node

I'm not sure I understand why an iRule would be necessary here. If you're just looking to ensure that all requests from a given client end up at the same webserver, you'd be talking about persistence, which can easily be enabled via the GUI in many different forms.

 

 

-Colin

 

You likely don't need an iRule. As Colin suggests, you need persistence. The persistence profile have a couple of settings to help solve your problem. Unless you decide to use cookie persistence, you will probably want to use the across virtuals and across pools settings to allow a persistence record to be applied to different pools.

 

 

You will want two virtuals - one for the http traffic and one for the https traffic. Then you will also have two pools - one pool for the http traffic and one pool for the https traffic but both with the same nodes. Then configure your persistence method and apply it to both virtuals.

dear unruley,

 

 

i have configured by following your advice and tried to login in many time. some time it's work but some time it isn't.

 

 

my configuration is

 

 

1. BIG/IP have been configured to use the same persistent profile (source_addr or cookie).

 

2. 2 virtual servers (different service port: 80 or 443)

 

3. 2 pools (the same host, different port: 80 or 443)

 

4. i tried to enable "match across pool" and "match across virtual" but it's still not work properly.

 

 

 

aue

What about "match across services"?

The straightforward way to do this is using source address affinity persistence plus across service.

 

 

If you would like to use cookie persistence, the across service might not work, then you have to use iRule to do this.