Your message dated Mon, 3 Sep 2007 08:31:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#440597: libapache2-mod-jk: fix for #425836 breaks "normal" rewriting with tomcat has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---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. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages libapache2-mod-jk depends on: ii apache2 2.2.3-4+etch1 Next generation, scalable, extenda ii apache2-mpm-prefork [a 2.2.3-4+etch1 Traditional model for Apache HTTPD ii apache2.2-common 2.2.3-4+etch1 Next generation, scalable, extenda ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries libapache2-mod-jk recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---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
--- End Message ---
