Bug#440597: libapache2-mod-jk: fix for #425836 breaks "normal" rewriting with tomcat

[Michael Koch]

On Mon, Sep 03, 2007 at 02:14:25AM +0200, Veit Guna wrote:
> Package: libapache2-mod-jk
> Version: 1:1.2.18-3etch1
> Severity: important
> 
> 
> Did an apt-get upgrade this evening with the effect that my apache2 rewriting with mod-jk for
> tomcat doesn't work out anymore. I'm using this simple rewriting rule:
> 
> RewriteEngine on
> RewriteCond %{REQUEST_URI} !^/(iurltoexcludefromtomcat|urltoexcludefromtomcat2)
> RewriteRule ^/(.*) /mytomcatcontext/$1 [PT]
> 
> Which rewrites all access to /foo to /mytomcatcontext/foo. This doesn't work out anymore.
> Instead of going to the /mytomcatcontext/foo, just /foo in tomcat is requested.
> 
> Took me a couple of hours to figure this out since _some_ packages changed regarding
> apache2 :(...
> 
> Downgrading to 1.2.18-3 fixes the issue for me.

The only change from 1.2.18-3 to 1.2.18-3etch1 was the change of the
default for URI forwarding (from apache httpd to apache tomcat). This
was made due to CVE-2007-1860. To get the old behavior use

  JkOptions     +ForwardURICompat

But beware. Thats a security risk. Please read the documentation at

  http://tomcat.apache.org/connectors-doc/reference/apache.html#Forwarding

for more infos.

Closing this bug as its not a bug.


Cheers,
Michael