From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Can Apache Proxy for a NAT'ed web-server
Date: Wed, 13 Jul 2005 11:38:14 +0800 [thread overview]
Message-ID: <1121225894.15192.152.camel@neuromancer.home.net> (raw)
I'm sure this can be done.
I know about mod_proxy and mod_proxy_html and it's functions as a
reverse proxy. But the thing is my current understanding of these
mod_proxy is it's suitable only for servers which are in the internal
network and has names such as
www.example.com -> external IP
internalserver.example.com -> NAT IP
external -> internalserver
www.example.com/internalserver (using mod_proxy and mod_proxy_html)
what if the NAT IP'ed server has it's own DNS? say www.example2.com.
Can apache still be used to get to it? using Mod_proxy?
I'm just trying to figure out if this is a valid scenerio.
--
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
98% Microsoft(tm) Free!!
Neuromancer 11:30:41 up 5 days, 19:27, 7 users, load average: 2.28,
1.63, 1.32
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2005-07-13 3:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121225894.15192.152.camel@neuromancer.home.net \
--to=ow.mun.heng@wdc.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox