An Exception to the iRule

In fact, our Big IP may not be the problem at all here. My task is to eliminate it as the culprit.

 

 

There is a wildcard dns entry that resolves a group of possible dns hostnames to a single IP address. The virtual server associated with this ip address has as a resource, an iRule which manages traffic that arrives at this IP address.

 

 

The irule in question looks like this:

 

 

when HTTP_REQUEST {

 

 

if {([HTTP::host] contains "hostname.com") and ([HTTP::uri] equals "/")} { HTTP::redirect

 

}

 

 

switch -glob [string tolower [HTTP::host]] {

 

 

"sponsor.hostname.com" { pool sponsor.hostname.com }

 

"sponsor-uat.hostname.com" { pool sponsor-uat.hostname.com }

 

 

}

 

 

}

 

 

There are a number of entries in this rule for various sponsors.

 

 

We experienced an issue today where connections intended for a sponsor.hostname.com pool instead, appeared to be directed to sponsor-uat.hostname.com.

 

 

The case matching seems to absolutely rule out the possibility of bleedover, but I am curious to hear if anybody has experienced an issue similar to this and would be willing to compare notes.

 

 

I look forward to hearing from anybody who has a similar experience to share or insights into this situation.

 

 

Matt