On Wed, Oct 9, 2013 at 2:17 PM, Mike Rumph mike.ru...@oracle.com wrote:
Okay, I've confirmed that the following configuration works for httpd
trunk and httpd 2.2.25:
RewriteEngine On
** **
RewriteCond %{HTTPS} =off
RewriteRule . - [E=protocol:http]
On Wed, Oct 16, 2013 at 8:49 AM, Jeff Trawick traw...@gmail.com wrote:
On Wed, Oct 9, 2013 at 2:17 PM, Mike Rumph mike.ru...@oracle.com wrote:
Okay, I've confirmed that the following configuration works for httpd
trunk and httpd 2.2.25:
RewriteEngine On
** **
RewriteCond
My bad.
Needs to be
RewriteRule ^/my_app/(.*) %{ENV:protocol}://1.2.3.4/my_app/$1 [P]
Regards
Rüdiger
From: Mike Rumph
Sent: Dienstag, 8. Oktober 2013 22:17
To: dev@httpd.apache.org
Subject: Re: [PATCH 55315] mod_proxy interpolation code broken by regression to
APR-util 1.5.2
Sorry.
I got
@httpd.apache.org
Subject: Re: [PATCH 55315] mod_proxy interpolation code broken by
regression to APR-util 1.5.2
Doesn't that completely avoid/ignore the issue in the 1st place?
On Sep 17, 2013, at 11:08 AM, Plüm, Rüdiger, Vodafone Group
ruediger.pl...@vodafone.com wrote:
How about
RewriteEngine
...@gmail.com]
Sent: Dienstag, 17. September 2013 15:24
To: Apache HTTP Server Development List
Subject: Re: [PATCH 55315] mod_proxy interpolation code broken by
regression to APR-util 1.5.2
On Wed, Sep 4, 2013 at 5:12 PM, Mike Rumphmike.ru...@oracle.com
wrote:
Hello Jeff,
Thanks for your reply.
On 9/3
On Sep 3, 2013, at 9:58 AM, Jeff Trawick traw...@gmail.com wrote:
The double use of ${} is nasty. In the fullness of time, I think that
mod_proxy interpolation should support an additional syntax that doesn't
collide with the config-time processing.
Agreed... as we expand mod_proxy
