Hi,
Just a confirmation:
- I did apply *only* this patch:
https://issues.apache.org/bugzilla/show_bug.cgi?id=47645#c13 described in
the link in comment #13.
I did not apply the other ones mentionned in comments #5 and #11
https://issues.apache.org/bugzilla/show_bug.cgi?id=47645#c11
https://issu
Sorry, I meant to write example.com...
I use include my RP-Rules in a dedicated file.
There I work with RewriteRule ^/(.*)$ http://internal.example.com/$1 [P,QSA,L]
ProxyPassReverse is used in a Location directive like
ProxyPassReverse /
The 302 Location is full qualified, so normaly
On Wed, 2013-08-21 at 08:30 +, Womann, Sven wrote:
> But on the client side, it is a redirect to
> http://www.server.com/login. That results in a loop.
Are you working for server.com, or did you mean to write example.com?
What ProxyPassReverse directives do you have?
If that isn't what you w
I will be out of the office starting 21.08.2013 and will not return until
22.08.2013.
Please contact Ms Louisa Ng at 2810 3065 if you need assistance.
This notice is generated in response to your mail:
From: users-digest-h...@httpd.apache.org
Subject: users Digest 21 Aug 2013 08:31:29 -
Hello,
I migrated my Apache 2.2 to 2.4. It is working as a reverse proxy. Now I have
the following issue:
For the listener on Port 80 I set a request header ClientProtocol=http.
For the listener on Port 443 I set it to https.
So my application on the backend knows for example that for a login i
