Redirect to Multiple URLs

Posted By Colin on 05/09/2008 5:29 PM

 

 

There isn't a good way that I can think of to do health-checks on remote sites. It's pretty easy to redirect users to wherever you want, but health-checking remote systems is a little more tricky.

 

 

Colin

 

 

 

I'm confused by this statement, Colin.

 

 

What's the difference?

 

 

If you setup a pool with a member that's remote (e.g. sample.domain.com) and setup a health monitor that performs 'GET /blah', surely this will do what the OP wanted...? mark the node down if the remote site doesn't respond to the GET /blah, thereby enabling the LB::status check.

 

 

What am I missing?

Hi

 

When sending the redirect back to the client, the client will initiate a new connection to a new destination. --> Server1 or Server2 Therefore no control over the connection within this irule anymore.

 

 

I think you now found the issue, that you would not reach the server 1 or 2 if it is down.

 

 

So i do not think you should work with redirect at all. Do you have control over those servers ?

 

Why do you need to work with a redirect ? Just Loadbalance the Servers with a pool and replace the hostheader if needed. (don´t think you need to)

 

 

Please explain us about the goal of the redirects a bit more that we are able to help

 

 

Wiesmann

 

Here's a revision that avoids Global Variables so as to be CMP safe.

when RULE_INIT {
  set static::redirect_targets {{https://www1.example.com/} {https://www2.example.com/} {https://www3.example.com/}}
}

when HTTP_REQUEST {
  HTTP::redirect [lindex $static::redirect_targets [expr {[table incr [virtual]_redirect_req_count] % [llength $static::redirect_targets]}]]
}