RE: [OT] IIS, domains, routers and host headers

["Paul Gale" <groups@xxxxxxx>]

Thanks Doogie - that made good sense :-)



One question though - what happens if I have two web sites setup with
ClientSite1 and ClientSite2 and ClientSite1 is mapped through the router
(domain of say ClientSite1.mydomain.com with a public IP address of course)
- the router forwards traffic for port 80 to the internal server on
192.168.0.1 - but ClientSite2 doesn't have a separate mapping or public
domain/IP etc. Is there any way of getting to ClientSite2 from the Internet
- how secure is it then? (Where does IIS get the header info from - browser
URL box???)



Did that question make sense?



Cheers,

Paul.



-----Original Message-----
From: Doogie Brodie [mailto:ukhad@xxxxxxx]
Sent: 29 August 2003 18:19
To: ukha_d@xxxxxxx
Subject: Re: [ukha_d] [OT] IIS, domains, routers and host headers



Paul Gale wrote:
>If possible I'd prefer to keep ports to 80. How do host headers work?

Hi Paul,

Host headers (in IIS assigned by going properties on the web site in IIS
management, choosing advanced beside IP Address, choosing add, and
putting in the host header name. You can then run multiple port 80 web
sites (new web site from a right click on server/web sites in IIS
management) and give them a different host header name.

You can then muck around with DNS, or with your local hosts file,
whichever you're more comfortable with.

Basically what I'd do for simplicity (!) is make several websites, eg
ClientSite1, ClientSite2, ClientSite3 in IIS, giving the sites the same
IP address and port, but host headers of ClientSite1, ClientSite2,
ClientSite3. I'd then go into the hosts file on the client/ dev machine
(c:\winnt\system32\drivers\etc\hosts) and add a static resolve in there for

192.168.0.10      ClientSite1
192.168.0.10      ClientSite2
192.168.0.10      ClientSite3

So on your client/ dev PC, you'd go http://ClientSite1 which your PC
would resolve to 192.168.0.10 which would then hit your IIS server which
would then look at the ClientSite1 host header and pick the ClientSite1
website to serve.

If that has confused the hell out of you, then it's probably something
to do with Friday afternoons :D


--
Doogie