Using filter in Web Farm

Topics: User Forum
Jan 29, 2007 at 3:13 PM
Thanks for this great app. I am trying to test this for a client of ours who is experiencing issues with their Computer Based Training modules not working correctly when they access our LMS w/o a FQDN in the URL (due to IE cross-domain script blocking). I configured the ini to work the way I want (converts IP or short hostname to FQDN), however, the issue is that our clients intranet is in a 4 node web farm using MS NLB. Users are supposed to access the farm with its designated FQDN, but sometimes they use short names, IP addresses, or even direct hits to individual nodes (bad...bad end users!!).

Is there any known way to get this filter to work in this sort of environment that would force the URL to use the FQDN of the farm address? For instance, the farm name users should access is http://webfarm.company.net/cbtlive. This would balance the request between 4 different IIS servers (i.e. web1.company.net, web2.company.net, etc). If users just go to http://webfarm/cbtlive, I would like some way to rewrite this to the proper address. The problem is that as far as I know, there is no way to work ISAPI filters into NLB (I am not real familiar with NLB though).

My initial presumption here is that if I try to rewrite the URL on each node, it will cause some sort of loop, and may interput the balancing affinity. I am working on setting up a test environment, but that is going to take a while so I thought I'd post here in the meantime to see if anyone has any ideas.

If anyone can provide some info on this, I would appreciate it. TYIA.
Coordinator
Feb 24, 2007 at 1:20 AM
Could you just include a rule that redirects based on the restricted URL patterns?
Redirect to a web page that says "please use the FQDN. This page will redirect you in 6 seconds."
and then have a HTTP Meta tag Refresh="http://fqdn/whatever".