Hi,
Nick Kew from the httpd-users list pointed me to the final solution:
The problem is, that the redirect is initiated through the Location
header, which can be rewrited with mod_headers:
Header edit Location ^([^/]*//[^/]*)?/spike/(.*)$ $1/$2
I think, mod_proxy should rewrite this header, to
On 27/04/2010 04:25, Timo Meinen wrote:
Is someone out there, who can explain me, what the problem is?
It looks like a bug in mod_proxy_ajp. Check you are using the latest
httpd release (2.2.15) and if you still see the problem, open a bug.
Note: mod_proxy_ajp is maintained by the httpd proje
Here are some debug information to this problem. The message is logged
just after the 302 redirect to the https. The Context-Path of the
application is /spike:
[Tue Apr 27 16:54:39 2010] [debug] mod_proxy_ajp.c(239): proxy:
APR_BUCKET_IS_EOS
[Tue Apr 27 16:54:39 2010] [debug] mod_proxy_ajp.c(244):
Is someone out there, who can explain me, what the problem is?
Does the ProxyPassReverse only removes the ContextPath if the protocol
(http/https) in the response is the same than in the request? Is it
possible to configure the Proxy to ignore the protocol information?
Thank you for any hint - I
Hi Hassan,
yes, there are two VirtualHost entries. One for port 80 and one for
port 443 with SSL engine enabled. Both have the same proxy
configuration.
Timo
2010/4/22 Hassan Schroeder :
> On Thu, Apr 22, 2010 at 3:25 AM, Timo Meinen
> wrote:
>
>> our configuration is a Apache 2.2 web server,
On Thu, Apr 22, 2010 at 3:25 AM, Timo Meinen wrote:
> our configuration is a Apache 2.2 web server, acting as a reverse
> proxy for Tomcat 6. This is the configuration:
> ServerName it.localhost.de
> ProxyPass / ajp://127.0.0.1:8009/spike/
> ProxyPassReverse /
Hi,
our configuration is a Apache 2.2 web server, acting as a reverse
proxy for Tomcat 6. This is the configuration:
ServerNameit.localhost.de
ProxyPass / ajp://127.0.0.1:8009/spike/
ProxyPassReverse/ ajp://127.0.0.1:8009/spike/
ProxyPassReverseCookiePath
