I'm sorry.  In rereading my post, I see now that I really wasn't very
clear at all.

By "host headers vs. CGI vars" I really meant to compare IIS' host
header handling to that of a CF script.  Are you aware of any voodoo
inside IIS that does a better job in directing incoming traffic by host
header than a CF script which parses the info from CGI.HTTP_HOST and
redirects via CFLocation?  Do both methods share 100% of the same
caveats?

Thank you.

Dave

-- 

David M. Delbridge
Circa 3000
ColdFusion Hosting
http://www.circa3k.com
775-832-2445


Dave Watts wrote:
> 
> > This brings up a relevant question I've had for some time:
> > Is there any difference in using host headers vs. CGI
> > variables to direct traffic based on requested URL? I've
> > been under the impression for some time that the latter
> > method bears certain caveats, for example, incompatibility
> > with some older browsers (though I've never personally
> > witnessed it). Would the same caveats apply exactly to host
> > headers on IIS or is this method somehow more robust?
> 
> I'm not sure I understand, exactly. When your browser sends a Host header
> (which any browser that supports HTTP/1.1 should send, I think), that is a
> CGI variable - CGI.HTTP_HOST in CF. Older browsers don't send the Host
> header, so those won't work with "name-based" virtual servers that require a
> host header.
> 
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> voice: (202) 797-5496
> fax: (202) 797-5444
> 
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. 
http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to