CSS 11150 (5.037) limitations?

[jan.sveide]

My webservers hosts multiple sites and naturally I use host header names because I only have ONE ip number. Each website have its webdata located on a NetApp filer on the network. When one website is disabled the corresponding service is still marked as Alive on the CSS. This is because the CSS still founds the index.html in the webservers wwwroot. When I try to change the "Keepalive method" to get and specify the uri to corresponding virtual site on the filer this makes the CSS mark the service as Down. This is because the CSS now doesn't found the index.html in the path. If I have made the right conclusion the CSS cannot handle host header names if the corresponding site have its webroot on a virtual folder.Is that so?And if not, how can i solve this extremely annoying issue?

[wong.bradley]

In my environment, I have one IIS server hosting multiple websites, such as one.widget.com, two.widget.com and three.widget.com. Instead of using keepalive uri "/index.html", i created one index.html on each virtual websites. Then, create one service for each virtual websites with keepalive uri of

service one-server

keepalive uri "http://one.widget.com/index.html"

.....

service two-server

keepalive uri "http://two.widget.com/index.html"

.....

service three-server

keepalive uri "http://three.widget.com/index.html"

.....

Similarly, create three content rules, one for each service. Each content rule will has the same vip address (because we only have one ip address). Of course, one.widget.com, two.widget.com and three.widget.com resolve the same ip address.

It works in my environment. I'm not familiar with NetApp filer. I don't know how it handles the host header, but it works with the IIS servers.

Hope this help.

Brad

[jmccarro]

The standard keepalive does not use a Host Tag. If your webservers require this then you should use the scripted keepalive ap-kal-httptag which will allow you to specify the hosttag. You will need a separate service for each instance.