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 hit the https part of the server. Is this just a bug or do I need to configure it in some special way?

Thanks,
Chris


Filip Hanik wrote:

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 JK connector.

Binary Downloads:
http://jakarta.apache.org/site/binindex.cgi

Source downloads:
http://jakarta.apache.org/site/sourceindex.cgi

Remy


--
Chris P. McCabe               - Principle Engineer
Choice Hotels International   - Information Technology
[EMAIL PROTECTED] - 602-953-4416



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to