Newbie: host header values & listening on same port

Newbie: host header values & listening on same port

am 22.01.2008 01:52:29 von Suzette

Hi. I have a simple scenario whereby I want people routed to web application
1 when they type in www.mywebsite.com in to their browser, and web
application 2 when they type in custom.mywebsite.com.

I have set something up that appears to work by creating two web sites, both
listening on port 80, one is the default website to trap www.mywebsite.com
whilst the other has the host header value set to custom.mywebsite.com.

My experience tells me that two applications cannot listen on the same port,
yet, it works.

Have I configured this right or is there a better way?

Thanks in advance!!!

McGeeky

Re: Newbie: host header values & listening on same port

am 22.01.2008 09:26:35 von David Wang

On Jan 21, 4:52=A0pm, "McGeeky" wrote:
> Hi. I have a simple scenario whereby I want people routed to web applicati=
on
> 1 when they type inwww.mywebsite.comin to their browser, and web
> application 2 when they type in custom.mywebsite.com.
>
> I have set something up that appears to work by creating two web sites, bo=
th
> listening on port 80, one is the default website to trapwww.mywebsite.com
> whilst the other has the host header value set to custom.mywebsite.com.
>
> My experience tells me that two applications cannot listen on the same por=
t,
> yet, it works.
>
> Have I configured this right or is there a better way?
>
> Thanks in advance!!!
>
> McGeeky


What you are doing is right.

There is still only one application listening on the port -- IIS. It
is multiplexing host headers into multiple websites which each has its
own web application.


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

Re: Newbie: host header values & listening on same port

am 22.01.2008 21:33:37 von Suzette

Thanks for confirming that for me.


"David Wang" wrote in message
news:dec48ade-7925-4754-bfa8-6d15dba4def6@k39g2000hsf.google groups.com...
On Jan 21, 4:52 pm, "McGeeky" wrote:
> Hi. I have a simple scenario whereby I want people routed to web
> application
> 1 when they type inwww.mywebsite.comin to their browser, and web
> application 2 when they type in custom.mywebsite.com.
>
> I have set something up that appears to work by creating two web sites,
> both
> listening on port 80, one is the default website to trapwww.mywebsite.com
> whilst the other has the host header value set to custom.mywebsite.com.
>
> My experience tells me that two applications cannot listen on the same
> port,
> yet, it works.
>
> Have I configured this right or is there a better way?
>
> Thanks in advance!!!
>
> McGeeky


What you are doing is right.

There is still only one application listening on the port -- IIS. It
is multiplexing host headers into multiple websites which each has its
own web application.


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