tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: Last few JK bugs in TC4
Date Wed, 22 Dec 2004 21:57:39 GMT

----- Original Message -----
From: "Mark Thomas" <>
To: "'Tomcat Developers List'" <>
Sent: Wednesday, December 22, 2004 1:05 PM
Subject: Last few JK bugs in TC4

> I have been going through the tomcat 4 JK2 bugs marking them as WONTFIX -
> about all those bugzilla e-mails ;) - and there are a few that look like
> are really JK bugs. Chances are that these are non-issues/already
> fixed/configuration problems but I lack the JK experience to tell. If
anyone who
> knows more about JK than I wants to cast their eyes over them that would
> great. If not, I'll just leave them to gather dust.
> The bug numbers are:
> 18342
Possibly fixed with Mladen's changes to the socket timeout in 1.2.8-RC1.

> 25055
Enhancement request at best (and not one that I like).  Security should be
done by Tomcat in this case.  mod_jk/Apache2 bypasses directory_walk, so
'.htaccess' is never looked at.

> 21146
It's an old mod_jk, so it might have been fixed.  Currently mod_jk and
mod_jk2 do the same thing here.

> 23105
Yup, known issue, and one of the reasons for proxy_ajp ;-).

> 27796
Fixed in j-t-c HEAD long ago.

> 19255
I don't believe that anybody is supporting the ant build for jk.  Even Gump
uses configure/make :).

> Cheers,
> Mark
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message