Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C63F97DD5 for ; Mon, 18 Jul 2011 21:27:15 +0000 (UTC) Received: (qmail 37323 invoked by uid 500); 18 Jul 2011 21:27:13 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 37258 invoked by uid 500); 18 Jul 2011 21:27:12 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 37250 invoked by uid 99); 18 Jul 2011 21:27:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2011 21:27:11 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jc_denton_1372@hotmail.com designates 65.55.34.89 as permitted sender) Received: from [65.55.34.89] (HELO col0-omc2-s15.col0.hotmail.com) (65.55.34.89) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2011 21:27:05 +0000 Received: from COL110-W34 ([65.55.34.71]) by col0-omc2-s15.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Jul 2011 14:26:45 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_203550fd-dde3-4586-8e7b-e36010839608_" X-Originating-IP: [125.236.56.121] From: Peter B To: Date: Tue, 19 Jul 2011 09:26:45 +1200 Importance: Normal In-Reply-To: <14514244.20688.1311023799226.JavaMail.root@co4> References: ,<14514244.20688.1311023799226.JavaMail.root@co4> MIME-Version: 1.0 X-OriginalArrivalTime: 18 Jul 2011 21:26:45.0704 (UTC) FILETIME=[652EC480:01CC4591] Subject: RE: [users@httpd] Virtual Hosts on physical servers --_203550fd-dde3-4586-8e7b-e36010839608_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Patrick=2C Do you know of any examples on how to configure this? > From: patrick.proniewski@univ-lyon2.fr > Date: Mon=2C 18 Jul 2011 23:16:36 +0200 > To: users@httpd.apache.org=3B jc_denton_1372@hotmail.com > Subject: Re: [users@httpd] Virtual Hosts on physical servers >=20 > Hi=2C >=20 > On 18 juil. 2011=2C at 21:20=2C Peter B wrote: >=20 > > I have a single IP address=2C with multiple web servers=2C so I somehow= need www.hello.com to go to server1 and www.test.com to go to server2. >=20 >=20 > As long as you have only one public IP address=2C you'll have to put a de= vice (sofware or hardware) between your servers (private IP addresses)=2C a= nd the internet. > That can be NAT=2C but the port issue is not very nice for clients. Or=2C= that can be a proxy=2C who will act almost like a NAT=2C but on the applic= ation level. > Your proxy can be an Apache Server=2C with mod_proxy=2C setup to forward = client requests for www.hello.com to server1=2C and www.test.com to server2= . That's not an unusual setup.=20 > That could also be a Layer 7 switch=2C but it's very expensive=2C doing e= xactly the same job (somewhat easier to configure). >=20 >=20 > Patrick PRONIEWSKI > --=20 > Administrateur Syst=E8me - DSI - Universit=E9 Lumi=E8re Lyon 2 >=20 = --_203550fd-dde3-4586-8e7b-e36010839608_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Patrick=2C Do you know of any examples on how to configure this?

>=3B From: patrick.proniewski@univ-lyon2.fr
>=3B Date: Mon=2C 18 J= ul 2011 23:16:36 +0200
>=3B To: users@httpd.apache.org=3B jc_denton_13= 72@hotmail.com
>=3B Subject: Re: [users@httpd] Virtual Hosts on physic= al servers
>=3B
>=3B Hi=2C
>=3B
>=3B On 18 juil. 2011= =2C at 21:20=2C Peter B wrote:
>=3B
>=3B >=3B I have a single = IP address=2C with multiple web servers=2C so I somehow need www.hello.com = to go to server1 and www.test.com to go to server2.
>=3B
>=3B >=3B As long as you have only one public IP address=2C you'll have to p= ut a device (sofware or hardware) between your servers (private IP addresse= s)=2C and the internet.
>=3B That can be NAT=2C but the port issue is = not very nice for clients. Or=2C that can be a proxy=2C who will act almost= like a NAT=2C but on the application level.
>=3B Your proxy can be an= Apache Server=2C with mod_proxy=2C setup to forward client requests for ww= w.hello.com to server1=2C and www.test.com to server2. That's not an unusua= l setup.
>=3B That could also be a Layer 7 switch=2C but it's very ex= pensive=2C doing exactly the same job (somewhat easier to configure).
&g= t=3B
>=3B
>=3B Patrick PRONIEWSKI
>=3B --
>=3B Admin= istrateur Syst=E8me - DSI - Universit=E9 Lumi=E8re Lyon 2
>=3B
= --_203550fd-dde3-4586-8e7b-e36010839608_--