Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of tevans.uk@googlemail.com
 designates 209.85.160.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=ZpJdi637hTzR8M9Ip4gv+2LblSPg/zDDTs+ulLi5XfloPq/hMf28pQH8nAp0JdTPZV
         S7oczypG9xwQRZn0xhdl+v2pCNey6WNhIyhfo+HqYk/wPZzAoTEODjBYyCVvj+JtkaEG
         QKCtnhags8Z803aMehw1WjgAtzGB/jHERdmfg=
MIME-Version: 1.0
In-Reply-To: <4C2B4B83.2070306@proximic.com>
References: <4C2B4B83.2070306@proximic.com>
Date: Wed, 30 Jun 2010 15:26:10 +0100
Message-ID: <AANLkTilAg_lV53fUBieaVJ0_JU65xaKofHNT2GlQ-J0A@mail.gmail.com>
From: Tom Evans <tevans.uk@googlemail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [users@httpd] Reverse Proxy with partial paths possible

On Wed, Jun 30, 2010 at 2:49 PM, Dirk Taggesell
<dirk.taggesell@proximic.com> wrote:
> Hi all,
>
> I run an Apache 2.2.11 for several virtual hosts and I configured
> several reverse proxy directives which are working as intended.
>
> Now I received a request to configure some additional rules, like these:
>
> ProxyPass =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /bla/ =C2=A0ht=
tp://first-back-end:8000/
> ProxyPassReverse =C2=A0 =C2=A0 =C2=A0 =C2=A0/bla/ =C2=A0http://first-back=
-end:8000/
>
> ProxyPass =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /bla/req http:=
//second-back-end:9200/req
> ProxyPassReverse =C2=A0 =C2=A0 =C2=A0 =C2=A0/bla/req http://second-back-e=
nd:9200/req
>
> While the first one works as intended, the second one is somewhat
> special: it is intended to route requests like this:
>
> http://frontend/req.txt?some=3Darguments&and=3Devensomemore
>
> as well as
>
> http://frontend/req.xml?some=3Darguments&and=3Devensomemore
>
> to the second backend. And introducing an additional path like
>
> http://frontend/path/req.xml?some=3Darguments&and=3Devensomemore
>
> is not allowed, though it would make the whole thing much easier.
>
> Can the desired behaviour being achieved with a simple reverse proxy
> directive? Or would I need ProxyReverseMatch or something?
>
> --
> kind regards
> Dirk Taggesell
>

This should work I think, but you have the order the wrong way around.
Put the most specific path first, the least specific last.

Eg:

ProxyPass /req http://app2/req
ProxyPassReverse /req http://app2/req
ProxyPass / http://app/
ProxyPassReverse / http://app/

Cheers

Tom

---------------------------------------------------------------------
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