[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: Wed, 06 Mar 2002 20:29:09 +0000
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
>
>So I pressume that paulgordon.homeup.net, gets forwarded onto your IIS
>server on the relevant port? IIS then replies so you could, for
example,
>respond with a list of URLS with the correct addresses to use
internally
>and
>externally.
>
Sort of. paulgordon.homeip.net resolves to the external IP address of my
router. The router has several port redirections configured, so that
incomming connections to port 80 go to port 80 on server1, connections to
port 81 go to port 80 on server2, and so on...
So currently, if I want to get to server2, I have to specify the
":81" in my
browser.
>Eg: http://paulgordon.homeip.net/index.html
replies with a list:-
><html>...
>* External IIS1 - http://paulgordon.homeip.net:81
>* External Linux - http://paulgordon.homeip.net:82
>* External HomeSear - http://paulgordon.homeip.net:83
>
>* Internal IIS1 - http://mybuggyiis/
>* Internal Linux - http://mrlinux/
>* Internal HomeSear - http://homesear/
>...</html>
>
>Now assuming what I've said above would work in your situation, its now
>just
>a case of writing a small bit of asp to do this automatically for you.
>http://paulgordon.homeip.net/server1/default.asp
needs to check some of the
>server variables in the request to determine if you got to it
externally or
>internally. Then it can redirect to the correct site. Remember that a
>redirect is just an 'object moved' response sent to your browser. The
>browser will send a new request to the new location, and so must be
valid
>to
>work.
>
It should work, - I can see that it should work. - however, I should also
be
able to do virtually the same thing automatically and cut out that step. -
I
set up additional virtual directories in IIS, called "server1"
and "server2"
or some such, and configure IIS to redirect them to another URL. The URL
will be the paulgordon.homeip.net, with the appropriate port number
added...
paulgordon.homeip.net/server1 then goes to paulgordon.homeip.net:81
paulgordon.homeip.net/server2 then goes to paulgordon.homeip.net:82
As you say, the redirect is just sent back to the browser to make a new
request to the specified URL, so this should work just as if the port
number
was specified originally.... then the new request hits my router, where the
port redirections do their stuff, exactly as they are doing now.
So all I have to use are the more memorable names that I choose to give the
virtual directories that represent each of my internal webservers.
seems like it should work to me!...
Paul G.
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe: ukha_d-subscribe@xxxxxxx
Unsubscribe: ukha_d-unsubscribe@xxxxxxx
List owner: ukha_d-owner@xxxxxxx
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Home |
Main Index |
Thread Index
|