Mark Thomas wrote:
Jess Holle wrote:
You're right -- this works fine in the direct case.
So I need to file a bug against mod_proxy_ajp instead? Or is there
some chance this is in the AJP connector?
Only if there is a bug - we haven't shown that yet ;)
Could you provide some version numbers please (httpd, mod_jk, etc)
Also, what setting are you using for JkOptions?
http://tomcat.apache.org/connectors-doc/reference/apache.html
I suspect you want
JkOptions +ForwardURICompatUnparsed
but read the docs carefully before making any changes so you
understand the security implications.
I don't believe mod_proxy_ajp provides any such options -- and I'm using
that and Apache 2.2.x, not 2.0.x and/or mod_jk. At any rate, I have:
<Proxy balancer://ajpWorker>
BalancerMember ajp://localhost:8010 min=16 max=80 smax=40
ttl=900 keepalive=Off timeout=90000 retry=1 flushpackets=on
</Proxy>
and
<IfModule mod_proxy_ajp.c>
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule ^(/MyWebAppName/(.*\.jsp(.*)|servlet/.*|.*\.jar))$
balancer://ajpWorker$1 [P]
</IfModule>
</IfModule>
which maps all JSP, servlet, and .jar requests to Tomcat and lets Apache
handle everything else.
--
Jess Holle
