iRule Issue

You are using strings as boolean expressions which is what is causing the error.

You could do something like this:

when HTTP_REQUEST {
  if { [HTTP::host] contains "www.careers.philips.com"} {
    HTTP::redirect "http://www.philips.com/about/careers"
  } elseif { ([HTTP::host] contains "www.peopleclick.com") or 
    ([HTTP::host] contains "eeosource.peopleclick.com") or 
    ([HTTP::host] contains "eeoanalytics.peopleclick.com") or 
    ([HTTP::host] contains "eeodiversity.peopleclick.com") or 
    ([HTTP::host] contains "generator.peopleclick.com") or 
    ([HTTP::host] contains "optimum.peopleclick.com") or 
    ([HTTP::host] contains "secure.peopleclick.com") or 
    ([HTTP::host] contains "strategichr.peopleclick.com") or 
    ([HTTP::host] contains "www.itiliti.com") or 
    ([HTTP::host] contains "www.eeosource.com") or 
    ([HTTP::host] contains "www.eeosource.net") or 
    ([HTTP::host] contains "www.eeosource.org") or 
    ([HTTP::host] contains "elearning.peopleclick.com") } {
    pool CorpWeb
  } else {
    pool ProdWeb
  }
}

A couple of optimizations, you might use the "equals" command instead of "contains" unless, that is, you want to cover extensions to those domain names.

Also, I'd look into using the matchclass command instead of all those or's. You can create a String Data Group and you could consolidate all those "or's" into a single line. Search the forums for "matchclass" and you'll find some examples.

-Joe

http://support.f5.com/kb/en-us/prod...aping.html

For the rate shaping, your principal issue is that you are running 9.x. That version of code is well past end-of-life. Having said that, as Chris says (but with link to 9.x guide):

• BIG-IP version v9.0 Configuration Guide for Local Traffic Management: Configuring Rate Shaping

For the long or set, the use of a glob switch is generally more readable:

when HTTP_REQUEST {
    switch -glob [string tolower [HTTP::host]] {
        "www.careers.philips.com*" {
            HTTP::redirect "http://www.philips.com/about/careers"
        }
        
        "www.peopleclick.com*" - 
        "eeosource.peopleclick.com*" - 
        "eeoanalytics.peopleclick.com*" - 
        "eeodiversity.peopleclick.com*" - 
        "generator.peopleclick.com*" - 
        "optimum.peopleclick.com*" - 
        "secure.peopleclick.com*" - 
        "strategichr.peopleclick.com*" - 
        "www.itiliti.com*" - 
        "www.eeosource.com*" - 
        "www.eeosource.net*" - 
        "www.eeosource.org*" - 
        "elearning.peopleclick.com*" {
            pool CorpWeb
        }
        
        default {
            pool ProdWeb
        }
    }
}

I assume you want the equivalent of starts_with rather than contains, but it is trivial to change the meaning.

But, as @drteeth (a dentist?) observes, matchclass is generally a superior way to achieve this sort of thing:

• matchclass

which would look something like this (assuming you've created a class called corp-web-hosts in which the indices are lower-case only hostnames):

when HTTP_REQUEST {
    if { [HTTP::host] starts_with "www.careers.philips.com"} {
        HTTP::redirect "http://www.philips.com/about/careers"
    }
    elseif { [matchclass host-match starts_with [string tolower [HTTP::host]]] } {
        pool CorpWeb
    }
    else {
        pool ProdWeb
    }
}

Strictly speaking, the else conditional is not required if the default pool for the Virtual Server is already set to ProdWeb.