On Tue, Oct 8, 2013 at 9:01 PM, Jim Jagielski wrote:
>
> On Oct 8, 2013, at 1:25 PM, Yann Ylavic wrote:
>
> > Helo,
> >
> > in the case where a ping is configured in a worker to check backend's
> connection (re)usability, ap_proxy_create_hdrbrgd will force
> r->expecting_100 (r1516930).
> >
> >
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]
RewriteCond %{HTTPS} =on
RewriteRule . - [E=protocol:https]
RewriteRule ^/my_app/(
On 02/10/2013 08:35, Kaspar Brand wrote:
> On 01.10.2013 12:15, Dr Stephen Henson wrote:
>> That's just OpenSSL internals though. To handle ServerInfo properly in
>> mod_ssl
>> IMHO you would need a new directive as there's no support for per-certificate
>> SSL_CONF commands: it wasn't intended to
On 09/10/2013 02:22, Trevor Perrin wrote:
> Hi Kaspar, Stephen,
>
> So I think where things stand is that the OpenSSL 1.0.2 branch is
> capable of handling ServerInfo on a per-algorithm basis, but it's not
> clear how to expose this through Apache.
>
> (My previous email was naive, I was thinking
Committed revision 1530603.
thx again!
On Oct 8, 2013, at 4:24 PM, Yann Ylavic wrote:
> Sure, here it is.
>
> Please note 2 chances compared to the previous patch (pasted) :
> - the slow path ap_request_has_body used last to compute do_100_continue,
> - step Three-and-a-Half moved into step 3,
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 c
