I thought I had the behavior of "localhost" on IIS figured out. I thought: *If I create site "A" in IIS, and leave the IP unassigned, then http://localhost/ will resolve to site "A" (so long as there are no other sites with unassigned IPs on the same port)
This worked on my development and staging servers, but it's not working on production. Instead, site "B" is appearing at http://localhost/. However, site "B" *does* have an IP assigned to it, and I can't see that it has any characteristics that would distinguish it as the default site. If I change site "A"s port to 81, I can access it with http://localhost:81/, but why is site "B" hogging localhost (on port 80)??? I need a good understanding of "localhost" (with regard to IIS) to be able to use Verity K2 Spider for multiple sites. Thanks, Jamie ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
