Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 62426 invoked from network); 24 Feb 2011 14:45:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2011 14:45:11 -0000 Received: (qmail 17536 invoked by uid 500); 24 Feb 2011 14:45:10 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 17230 invoked by uid 500); 24 Feb 2011 14:45:08 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 17222 invoked by uid 99); 24 Feb 2011 14:45:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 14:45:07 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of burgoyne@keenuh.com designates 67.222.54.6 as permitted sender) Received: from [67.222.54.6] (HELO cpoproxy3-pub.bluehost.com) (67.222.54.6) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 24 Feb 2011 14:45:01 +0000 Received: (qmail 16591 invoked by uid 0); 24 Feb 2011 14:44:41 -0000 Received: from unknown (HELO box548.bluehost.com) (74.220.219.148) by cpoproxy3.bluehost.com with SMTP; 24 Feb 2011 14:44:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=keenuh.com; h=Message-ID:In-Reply-To:References:Date:Subject:From:To:Reply-To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance:X-Identified-User; b=DaOfyjlRl+eHfCIGAruiIElXVA981RiWlfyJSJ5sqZtt5Lo+7tic7BrGZ/pxGO6e2dQ4SgCNsYox86yu2T7bsgDXeAr90O9dXQr7aviT3GIDg9WQxAiM0OQkGmHLcGZN; Received: from localhost ([127.0.0.1] helo=box201.bluehost.com) by box548.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1PscQq-0000iu-U9 for dev@httpd.apache.org; Thu, 24 Feb 2011 07:44:41 -0700 Received: from 192.197.178.2 ([192.197.178.2]) (proxying for 142.53.63.186) (SquirrelMail authenticated user burgoyne@keenuh.com) by box201.bluehost.com with HTTP; Thu, 24 Feb 2011 09:44:40 -0500 Message-ID: <57561e49cc472c5d6f1cfb1013397423.squirrel@box201.bluehost.com> In-Reply-To: <51854c94cb3163c71ffbeb5d41cbcf26.squirrel@box201.bluehost.com> References:

<51854c94cb3163c71ffbeb5d41cbcf26.squirrel@box201.bluehost.com> Date: Thu, 24 Feb 2011 09:44:40 -0500 Subject: Re: ProxyPreserveHost - added functionality From: "Jeffrey E Burgoyne" To: dev@httpd.apache.org Reply-To: burgoyne@keenuh.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Identified-User: {2835:box548.bluehost.com:keenuhco:keenuh.com} {sentby:program running on server} Sorry, should have read it closer, change my example to : ProxyPass http://otherserver.com/cgi-bin > > > > So I just went with that style. > > > >> On Wed, Feb 23, 2011 at 7:12 PM, Jeffrey E Burgoyne >> >> wrote: >>> I am doing some work with a large organization that has recently >>> acquired >>> two products that work properly through a reverse proxy system only >>> when >>> ProxyPreserveHost is set to on. >>> >>> The organization had issue as they are mandated to have only a single >>> hostname as a point of entry for their web applications. They have many >>> technologies in the backend for web applications, and use different >>> context roots and proxies to manage a reverse proxy system to a few >>> dozen >>> back end boxes. >>> >>> As ProxyPreserveHost can only work on a virtual host level, I could not >>> properly configure the web server to deal both with these applications >>> and >>> the current configuration at the same time (as it broke all the back >>> end >>> technologies). >>> >>> >>> To solve this I made changes to mod_proxy specifically for them, but if >>> there is interest I can provide the code changes back to apache to >>> incorporate into the next release. >>> >>> Effectively, I added a new command that mirrors the idea of separate >>> ProxyPass lines, example : >>> >>> ProxyPreserveHostURL /idm/ >>> ProxyPreserveHostURL /SepApp/ >>> >>> >>> This effectively does the same as PreserveProxyHost, but only when the >>> URL's start off with the supplied parameter. >>> >>> >> >> Would it not be simpler to just expand ProxyPreserveHost to be valid >> in a directory context? >> >> Cheers >> >> Tom >> > > > -- > Jeffrey Burgoyne > Chief Technology Officer > KCSI Keenuh Consulting Services Inc > www.keenuh.com > burgoyne@keenuh.com > > > -- Jeffrey Burgoyne Chief Technology Officer KCSI Keenuh Consulting Services Inc www.keenuh.com burgoyne@keenuh.com