Bug#429751: 400 status code response from libapache2-mod-jk when used with mod-rewrite

[Michael Koch]

On Tue, Jun 19, 2007 at 05:00:26PM -0500, Andy Hamilton wrote:
> Package: libapache2-mod-jk
> Version: 1:1.2.23-2
> Severity: normal
> 
> I have apache2 (version 2.2.3-4) setup in front of a tomcat5.5 (version 
> 5.5.20-2) installation, and use libapache2-mod-jk for the connection 
> between them.
> 
> With the introduction of version 1.2.23-1 into testing, I noticed an 
> issue after reloading apache's modules. In my investigation, I also 
> tested version 1.2.23-2 from unstable, with the same results. All the 
> snippets from logs from my investigation were using 1.2.21-1 
> and 1.2.23-2.

The problem seems to be related to the ForwardURICompatUnparsed-Option
being default since mod_jk 1.2.23. This was made default because of the
security advisory CVS-2007-1860. When you are sure this security issue
can't be exposed on your system please change the default options to us
ForwardURICompat instead of ForwardURICompatUnparsed. This re-enables
the old behavior:

JkOptions     +ForwardURICompat

Please report back if this fixes your issues.


Cheers,
Michael
-- 
 .''`.  | Michael Koch <konqueror at gmx.de>
: :' :  | Free Java Developer <http://www.classpath.org>
`. `'   |
  `-    | 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B