Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Mon, 05 Nov 2007 10:19:20 -0500
Subject: Re: Proxying subrequests
From: "Akins, Brian" <Brian.Akins@turner.com>
To: "dev@httpd.apache.org" <dev@httpd.apache.org>
Message-ID: <C3549EA8.9B084%Brian.Akins@turner.com>
Thread-Topic: Proxying subrequests
Thread-Index: Acgc4ckqDsOKWs2cTj27HDshH8+gAgC3XOuv
In-Reply-To: <472A65B2.4070800@holsman.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 11/1/07 6:48 PM, "Ian Holsman" <lists@holsman.net> wrote:

> Akins, Brian wrote:
>> -1 from me (if that counts.)
>> 
>> Using ProxyPass should be fine for 95% of the use cases??
>> 
>> ProxyPass /cnn http://www.cnn.com/
>> 
>> <!--#include virtual="/cnn/WORLD/index.html" -->
>>  
> 
> yes.
> if you:
> a. have a static small number of hosts
> b. those hosts don't change often
> 
> if either of these 2 conditions aren't met, then proxypass is next to
> useless.

True. (You could manage with a decent config tool, however.)

Couldn't some creative rewrite rules do the same thing:

RewriteCond %{IS_SUBREQ} true
RewriteRule ^/proxy/(.*) http://$1 [P,L]

Note: not sure if that will actually work.

I just foresee horrible cross-site type "vulnerabilities" in this.
 
If it is configurable on/off, then I'm -0.


-- 
Brian Akins
Chief Operations Engineer
Turner Digital Media Technologies