Bug#440597: closed by Michael Koch <konqueror at gmx.de> (Re: Bug#440597: libapache2-mod-jk: fix for #425836 breaks "normal" rewriting with tomcat)

[Veit Guna]

Ok then.

In future it would be really helpful if "default-changes" would be
announce via changelog or similar in the package. Because the default
behavior
changes (keyword: backward compatibility) I think many other
installations will break without the admins knowledge.

Regards,
Veit

Debian Bug Tracking System schrieb:
> This is an automatic notification regarding your Bug report
> #440597: libapache2-mod-jk: fix for #425836 breaks "normal" rewriting with tomcat,
> which was filed against the libapache2-mod-jk package.
>
> It has been closed by Michael Koch <konqueror at gmx.de>.
>
> Their explanation is attached below.  If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact Michael Koch <konqueror at gmx.de> by replying
> to this email.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
>
>   
>
> ------------------------------------------------------------------------
>
> Betreff:
> Re: Bug#440597: libapache2-mod-jk: fix for #425836 breaks "normal"
> rewriting with tomcat
> Von:
> Michael Koch <konqueror at gmx.de>
> Datum:
> Mon, 3 Sep 2007 08:31:50 +0200
> An:
> Veit Guna <death at ruhries.org>, 440597 at bugs.debian.org
>
> An:
> Veit Guna <death at ruhries.org>, 440597 at bugs.debian.org
> CC:
> 440597-done at bugs.debian.org
>
>
> 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
>