Bug#440597: closed by Michael Koch [EMAIL PROTECTED] (Re: Bug#440597: libapache2-mod-jk: fix for #425836 breaks normal rewriting with tomcat)
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 [EMAIL PROTECTED].
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]
Datum:
Mon, 3 Sep 2007 08:31:50 +0200
An:
Veit Guna [EMAIL PROTECTED], [EMAIL PROTECTED]
An:
Veit Guna [EMAIL PROTECTED], [EMAIL PROTECTED]
CC:
[EMAIL PROTECTED]
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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440597: closed by Michael Koch [EMAIL PROTECTED] (Re: Bug#440597: libapache2-mod-jk: fix for #425836 breaks normal rewriting with tomcat)
Hi again. 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 Actually that doesn't work out. Tried it with the same effect that forwarding breaks. Regards, Veit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440597: libapache2-mod-jk: fix for #425836 breaks normal rewriting with tomcat
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 apache22.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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440597: libapache2-mod-jk: fix for #425836 breaks normal rewriting with tomcat
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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
