alternate web server via host headers setup

so i can setup iis to do the following?
-for 2 domain names (dns) both pointing to my router (mydomain1.com +
mydomain2.com)
and the router sends all port 80 traffic to the
iis machine, say 192.168.0.100, so traffic for
both is coming in on port 80, and browser users only have to provide domain
name without any port number in the url
-for iis to serve mydomain1.com, put all its files in the default iis 'home'
directory, a usual iis website (or even set up that dn on a virtual web
site)
-to have mydomain2.com served by zope on another machine, say 192.168.0.101,
where zope listens on 80, to make this happen configure iis as below
for default web site properties
select website tab
select advanced (brings up 'mult identities for this website')
select add (brings up 'adv website identification')
ip address = 192.168.0.101
tcp port = 80
host header name = mydomain2.com
so all http port 80 traffic for mydomain2.com will get sent (like a pass
thru) to, 192.168.0.101 where it will
be served by the zope server? (and the zope pages sent back out, i'm
guessing, will go right out thru the router
which is the gateway for the zope machine and not pass thru iis on the way
out?)

Re: alternate web server via host headers setup

On Aug 28, 10:38 am, "bbxrider" wrote:
> so i can setup iis to do the following?
> -for 2 domain names (dns) both pointing to my router (mydomain1.com +
> mydomain2.com)
> and the router sends all port 80 traffic to the
> iis machine, say 192.168.0.100, so traffic for
> both is coming in on port 80, and browser users only have to provide domain
> name without any port number in the url
> -for iis to serve mydomain1.com, put all its files in the default iis 'home'
> directory, a usual iis website (or even set up that dn on a virtual web
> site)
> -to have mydomain2.com served by zope on another machine, say 192.168.0.101,
> where zope listens on 80, to make this happen configure iis as below
> for default web site properties
> select website tab
> select advanced (brings up 'mult identities for this website')
> select add (brings up 'adv website identification')
> ip address = 192.168.0.101
> tcp port = 80
> host header name = mydomain2.com
> so all http port 80 traffic for mydomain2.com will get sent (like a pass
> thru) to, 192.168.0.101 where it will
> be served by the zope server? (and the zope pages sent back out, i'm
> guessing, will go right out thru the router
> which is the gateway for the zope machine and not pass thru iis on the way
> out?)


Your best bet is to simply configure the router to forward
mydomain1.com to the IIS machine and mydomain2.com to the Zope
machine. Why do you even need to route requests to mydomain2.com
through the IIS machine?

You want routing based on HTTP host headers. That's a task for your
router to handle. If you want to make IIS route requests like that, it
means the router is inadequate for your scenario and has nothing to do
with IIS.

FYI: your entire logic of having mydomain2.com served by zope on
another machine is incorrect. It is not how networking works.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: alternate web server via host headers setup

thanks for the reply
i'm checking again but i dont think the netopia 3346n has host header
routing capability
that is the router that came with at+t dsl service, and there is no budget
for another router
but it seems i'm missing something here, so then what is the purpose of iis
having host header
capability to another machine if that should only be done by a router? why
would ms spend the effort to create that
if it should only be done by a router? in this case is a very small number
of websites with not that much traffic.
this sounds perhaps getting to more like a philosphical discussion and
based on the amount of hits involved.

i only wanted to know if iis host header functionality can route http route
80 traffic based on domain name to another machine
where a web server running on that machine can then service the website for
that domain name.




"David Wang" wrote in message
news:1188339219.143229.156850@q3g2000prf.googlegroups.com...
> On Aug 28, 10:38 am, "bbxrider" wrote:
>> so i can setup iis to do the following?
>> -for 2 domain names (dns) both pointing to my router (mydomain1.com +
>> mydomain2.com)
>> and the router sends all port 80 traffic to the
>> iis machine, say 192.168.0.100, so traffic for
>> both is coming in on port 80, and browser users only have to provide
>> domain
>> name without any port number in the url
>> -for iis to serve mydomain1.com, put all its files in the default iis
>> 'home'
>> directory, a usual iis website (or even set up that dn on a virtual web
>> site)
>> -to have mydomain2.com served by zope on another machine, say
>> 192.168.0.101,
>> where zope listens on 80, to make this happen configure iis as below
>> for default web site properties
>> select website tab
>> select advanced (brings up 'mult identities for this website')
>> select add (brings up 'adv website identification')
>> ip address = 192.168.0.101
>> tcp port = 80
>> host header name = mydomain2.com
>> so all http port 80 traffic for mydomain2.com will get sent (like a pass
>> thru) to, 192.168.0.101 where it will
>> be served by the zope server? (and the zope pages sent back out, i'm
>> guessing, will go right out thru the router
>> which is the gateway for the zope machine and not pass thru iis on the
>> way
>> out?)
>
>
> Your best bet is to simply configure the router to forward
> mydomain1.com to the IIS machine and mydomain2.com to the Zope
> machine. Why do you even need to route requests to mydomain2.com
> through the IIS machine?
>
> You want routing based on HTTP host headers. That's a task for your
> router to handle. If you want to make IIS route requests like that, it
> means the router is inadequate for your scenario and has nothing to do
> with IIS.
>
> FYI: your entire logic of having mydomain2.com served by zope on
> another machine is incorrect. It is not how networking works.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>

Re: alternate web server via host headers setup

Yes, you are misunderstanding the purpose of Host header support.

Host header support is a requirement from the HTTP/1.1 specification
-- nothing to do with MS, philosophical discussion, etc -- and it is a
very powerful feature on its own merit. It is actually required for
you to do what you want, but it does not do what you want on its own.

What you are asking for is *not* host header support. You are asking
for request forwarding / reverse proxying, which is something very
native to routers, and it can also be accomplished by IIS via a 3rd
party plug-in.

Thus, host header support probably does not look so interesting to
you... but that hardly means that it is insignificant.

Basically, you have two internal web servers servicing two different
domain names that have the same IP but different hostname. Something
needs to route traffic based on host header, and the network traffic
either looks like:

1. Router does routing based on host header:
Domain1 <---> Router <---> Server1
Domain2 <---> Router <---> Server2

2. Server1 does routing based on host header:
Domain1 <---> Router <---> Server1
Domain2 <---> Router <---> Server1 <---> Server2

As you can see, it is most efficient when router does the routing. If
you use request forwarding from Server1, it will always be involved in
all transactions to Server2, which makes Server1 a potential
bottleneck (remember, it is handling the request connection load for
both Server1 and Server2).


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Aug 29, 1:04 am, "bbxrider" wrote:
> thanks for the reply
> i'm checking again but i dont think the netopia 3346n has host header
> routing capability
> that is the router that came with at+t dsl service, and there is no budget
> for another router
> but it seems i'm missing something here, so then what is the purpose of iis
> having host header
> capability to another machine if that should only be done by a router? why
> would ms spend the effort to create that
> if it should only be done by a router? in this case is a very small number
> of websites with not that much traffic.
> this sounds perhaps getting to more like a philosphical discussion and
> based on the amount of hits involved.
>
> i only wanted to know if iis host header functionality can route http route
> 80 traffic based on domain name to another machine
> where a web server running on that machine can then service the website for
> that domain name.
>
> "David Wang" wrote in message
>
> news:1188339219.143229.156850@q3g2000prf.googlegroups.com...
>
>
>
> > On Aug 28, 10:38 am, "bbxrider" wrote:
> >> so i can setup iis to do the following?
> >> -for 2 domain names (dns) both pointing to my router (mydomain1.com +
> >> mydomain2.com)
> >> and the router sends all port 80 traffic to the
> >> iis machine, say 192.168.0.100, so traffic for
> >> both is coming in on port 80, and browser users only have to provide
> >> domain
> >> name without any port number in the url
> >> -for iis to serve mydomain1.com, put all its files in the default iis
> >> 'home'
> >> directory, a usual iis website (or even set up that dn on a virtual web
> >> site)
> >> -to have mydomain2.com served by zope on another machine, say
> >> 192.168.0.101,
> >> where zope listens on 80, to make this happen configure iis as below
> >> for default web site properties
> >> select website tab
> >> select advanced (brings up 'mult identities for this website')
> >> select add (brings up 'adv website identification')
> >> ip address = 192.168.0.101
> >> tcp port = 80
> >> host header name = mydomain2.com
> >> so all http port 80 traffic for mydomain2.com will get sent (like a pass
> >> thru) to, 192.168.0.101 where it will
> >> be served by the zope server? (and the zope pages sent back out, i'm
> >> guessing, will go right out thru the router
> >> which is the gateway for the zope machine and not pass thru iis on the
> >> way
> >> out?)
>
> > Your best bet is to simply configure the router to forward
> > mydomain1.com to the IIS machine and mydomain2.com to the Zope
> > machine. Why do you even need to route requests to mydomain2.com
> > through the IIS machine?
>
> > You want routing based on HTTP host headers. That's a task for your
> > router to handle. If you want to make IIS route requests like that, it
> > means the router is inadequate for your scenario and has nothing to do
> > with IIS.
>
> > FYI: your entire logic of having mydomain2.com served by zope on
> > another machine is incorrect. It is not how networking works.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -