Forum Discussion
Joe_Pipitone
Nimbostratus
NimbostratusHost headers on BigIP rather than IIS
I've submitted a support ticket to F5, however I'm not sure they understood what I am trying to accomplish. I am trying to have the BigIP handle host headers, rather than our front end IIS web servers.
I have a number of different virtual servers configured for each one of our websites (40 total)
Each virtual server is associated with a pool. My naming convention is as follows:
VIP-sitename-80
Pool-sitename-80
Each pool has the same 6 members (each are Windows 2003 IIS web servers)
Each IIS web server has 40 websites configured on each, and each website config has its own set of host headers. All websites serve content on port 80 - which was possible by using host headers.
Can anyone tell me if its possible using an iRule, to simply send traffic to a certain IIS site if a host name is matched?
For example, I know it is possible to use an iRule to do the following:
when HTTP_REQUEST {
if {[string tolower [HTTP::host]] eq "www.oursite.com"} {
pool Pool-sitename-80
}
}
Michael_YatesThe F5 LTM doesn't care about Host Headers. It only cares about the Port.
Look at it like this. You use the iRules to shape the Traffic to the Pools.
http://www.website.com/subcontent/index.html
If TCP Port == 80
Do something
If [HTTP::host] equals "www.website.com"
Do something (HTTP::Redirect or pool Pool-www.website.com-80)
If [HTTP::uri] equals "/subcontent/index.html"
Do something (HTTP::uri "/subcontent/index.asp" or pool Pool-www.website.com-80)
All of the iRule processing allows you to shape or change the traffic, but when it comes to the server, it only cares about what is configured in the Pool:
10.10.10.10 - Port 80
20.20.20.20 - Port 80
etc...
With the Senario that you have given you could use a single Virtual Server and a Single Pool to handle all 40 websites (Because they all exist on the same server and port). The LTM won't help you do what it is your wanting.
A solution to your problem (this is what I do on my IIS Servers) is to get rid of Host Headers by running your websites on Non-Standard Ports (Example: Port 5050). It removes the need for Host Headers, prevents the need for additional IP Addresses being wasted, and makes things easier to manage (in my opinion).
Hope this Helps.
Joe_PipitoneThanks Michael - I was thinking the same thing as far as using non-standard ports.
With that being said - how are you rewriting the port numbers so it is transparent to the client? Lets say I go to www.website1.com and the bigip sends traffic to a pool that contains a pool member 10.10.3.1 on port 5091, is there a way to rewrite that so it appears as port 80 for the client? Transparency?