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.212.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1355010305.5531.9.camel@fermat.scientia.net>
References: <1355010305.5531.9.camel@fermat.scientia.net>
Date: Mon, 10 Dec 2012 14:44:04 +0000
Message-ID: 
 <CAFHbX1KaR0FT0=n3QFQ0cMkyRVW08-SedXMLHLMR1xc1t414Ag@mail.gmail.com>
From: Tom Evans <tevans.uk@googlemail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [users@httpd] how to use ProxyPassReverse* with more complex a
 ProxyPassMatch

On Sat, Dec 8, 2012 at 11:45 PM, Christoph Anton Mitterer
<calestyo@scientia.net> wrote:
> Hi.
>
> I'm using a reverse proxy set up with ProxyPassMatch as the space I map
> to is rather complex and can't be mapped with a normal ProxyPass.
>
>
> Now the problem is obviously that:
> ProxyPassReverse
> ProxyPassReverseCookieDomain
> ProxyPassReverseCookiePath
> are only made for the simply ProxyPass form and there are no
> ProxyPassReverseMatch* versions.
>
> Is this planned and is there some way to work around this in the
> meantime?
>
>
> Thanks,
> Chris.

Use ProxyPassReverse, or simplify your application's urlspace such
that you can use ProxyPassReverse. You may have to explain why you
cannot use ProxyPassReverse, eg by supplying a sample scenario.

Cheers

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org