I am happy to report that the new mod_jk2.so from version 4.1.18 of
jakarta-tomcat-connectors fixed this problem.
Chris
Chris McCabe wrote:
I got the JK2 connector module working fine with Apache2 and Tomcat,
but when I try to access my secure server, I get a 404 Not Found error
from
Chris McCabe wrote:
This new release made no difference in the behavior of the JK2 connector
with an https connection, so my question remains:
Does anyone know the secret formula to get a JK2 connector to work with
both the http and https connection of the Apache2 web server? I get a
404 Not
Martin Jacobson wrote:
Chris McCabe wrote:
This new release made no difference in the behavior of the JK2
connector with an https connection, so my question remains:
Does anyone know the secret formula to get a JK2 connector to work
with both the http and https connection of the Apache2
resend,
Tomcat 4.1.18 has just been released, and includes a fix for an object
recylcing bug which could be exploited by a denial of service attack.
The bug was introduced in Tomcat 4.1.16 Beta, and is still present in
Tomcat 4.1.17 Stable. The release also includes a fix for SSL handling
in the
This new release made no difference in the behavior of the JK2 connector
with an https connection, so my question remains:
Does anyone know the secret formula to get a JK2 connector to work with
both the http and https connection of the Apache2 web server? I get a
404 Not Found error when I
