[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
RE: OT: (ish) Web publishing question
- To: ukha_d@xxxxxxx
- Subject: RE: OT: (ish) Web publishing question
- From: "Paul Gordon" <paul_gordon@xxxxxxx>
- Date: Thu, 07 Mar 2002 00:00:21 +0000
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
>>
>Paul,
>You can set up virtual directories/domain etc but that still means that
>*IIS
>has to serve them*, our problem is that we want to run multiple
(different)
>webservers on the same port - which can't be done...
>
>Lee.
>
I'm not sure what you mean by IIS has to serve them, - when creating the
new
default directory it has to be pointed initially to a real directory, which
can be either a local one, or a network share, but the choice is
irrelevant,
because as soon as the wizard has finished and the new virtual directory is
created, I change the properties so that the content selection changes from
"A directory located on this computer" to "A redirection to
a URL" then
specify "www.paulgordon.homeip.net:82" as the URL to redirect to.
NO content has to be served to the browser from the IIS machine the new URL
gets passed back to the client which then requests it as normal. Then,
because it is a *NEW* request on a different port number, my router's
redirection sends it to the requisite server on my LAN, on THAT machines
standard http port 80.
so I _can_ publish multiple internal webservers all on port 80 - but I _do_
need the client request to come in on the alternate port number eventually,
so that the router knows which server the request is for...
Paul G.
_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
Home |
Main Index |
Thread Index
|