Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of azzera.alan@gmail.com
 designates 209.85.198.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=FiXrzVs1lY8q67fH663Y227ckAlcZAiebTIZH8nzbt+NLpFR1MaR1lmUpJG5BTX0v++kayHI7RIH8l4WBL08oRD7u9ak/m7fFuY8bHDxe8piiYiiYnhH6u+WPYAYiLMlwJpGHXq+5WLuDSdOLDbGPVAlA67isOHccbMH/i1owdE=
Message-ID: <15484a840710221406s599789bbj8ed386199a3447a1@mail.gmail.com>
Date: Mon, 22 Oct 2007 23:06:29 +0200
From: "Alan AZZERA" <azzera.alan@gmail.com>
To: users@httpd.apache.org
In-Reply-To: <20071022063041.GB26623@w032y7.pnet.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <15484a840710190454w3415ed2cwe761ba747497856d@mail.gmail.com>
	 <20071019120211.GA11648@w032y7.pnet.ch>
	 <15484a840710190632k64012904g8674001d0114fe27@mail.gmail.com>
	 <20071019142246.GB13912@w032y7.pnet.ch>
	 <15484a840710191209o5b21662eu2e314efe3a1dfa06@mail.gmail.com>
	 <20071022063041.GB26623@w032y7.pnet.ch>
Subject: Re: [users@httpd] Need help to deal with poorly written PHP apps
 behind Apache used as Reverse Proxy

'nite

I'll try your tips tomorrow. Thanks a lot.

> If you want to get your hands really dirty, you can also
> leave mod_headers aside and set www.example.com statically
> in /etc/hosts to point to the backend. That way the proxy
> server will still believe that he is www.example.com via
> servername, but when you proxy to www.example.com it will
> go to the backend via /etc/hosts with the right host-header
> to let the backend generate the correct URLs. Not that I
> would recommend it, but I have seen this in practice...

I thought about another approach : leaving as is my public DNS zone,
and modifying my private one to distribute private IP for public
domain names. My Reverse Proxies have just to be taught to use the
private DNS, and all I have to do is to configure the VH
app.public.zone with ProxyPass / app.public.zone, app.public.zone
being resolved to the IP app.private.zone had previously.

Seems to be the same idea you describe, but with more flexibility &
robustness - thanks to real DNS records.

Anothet thanks. Regards,

Al.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org