From: "Nathan Cassano" <nathan@cjhunter.com>
To: 'alan barrow' <aaa.coms.sec@btclick.com>, netfilter@lists.samba.org
Subject: RE: a discussion starter i hope.
Date: Thu, 13 Jun 2002 09:30:45 -0700 [thread overview]
Message-ID: <0b1a01c212f7$ab1b9990$2901a8c0@amos> (raw)
In-Reply-To: <1020984749.22168.19.camel@sarig.internal>
Hi Alan,
> Now behind the firewall are 2 separate servers, each running a web
> service and each running on port 80.
>
> 1) The question is, with only 1 real world address available to you,
> what suggestions do you guy's have as to the configuration required to
> make both web servers available on the Internet ? So that incoming
port
> 80 request on the firewall public interface go to the correct server.
If you are solely interested in distributing http requests from a single
access point I would suggest running apache as a reverse proxy on your
firewall. This way http requests for different domains can be directed
to different internal (or external) web servers. Optionally this could
be done on layer 4 with DNAT, by rewriting the destination of packets
and perhaps adding a user level program to direct packets but I am less
knowledgeable about the implementation of such a setup.
Here is a simple example of a reverse proxy apache configuration.
<VirtualHost *:80>
DocumentRoot "/usr/local/apache/htdocs/server.tld"
ServerName public.server.tld
# Rewrite URL to back-end server URL
RewriteEngine on
RewriteLog logs/proxy_rewrite
RewriteLogLevel 0
RewriteRule ^/(.*)$ http://www1.server.internal/$1 [P]
# Reverse Proxy the requested URL
ProxyRequests on
ProxyVia on
ProxyPassReverse / http://www1.server.internal/
</VirtualHost>
next prev parent reply other threads:[~2002-06-13 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 22:52 a discussion starter i hope alan barrow
2002-06-13 16:30 ` Nathan Cassano [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-09 20:11 alan barrow
2002-06-13 16:13 ` Antony Stone
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='0b1a01c212f7$ab1b9990$2901a8c0@amos' \
--to=nathan@cjhunter.com \
--cc=aaa.coms.sec@btclick.com \
--cc=netfilter@lists.samba.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