Ian Ward Comfort wrote:
I don't know if this is intended behavior, or a bug in mod_jk, or even a
bug in Apache, but something seems amiss. Thoughts?
Your patch won't work.
The real problem is in the initialization for vhosts where
when there is *any* Jk directive the create_jk_config is
On Nov 2, 2007, at 12:44 AM, Ian Ward Comfort wrote:
I can't seem to find the repository location anywhere on the
connectors page either...
Ah, found it on the Tomcat pages.
--
Ian Ward Comfort [EMAIL PROTECTED]
System Administrator, Student Computing, Stanford University
On Nov 2, 2007, at 12:32 AM, Mladen Turk wrote:
Ian Ward Comfort wrote:
I don't know if this is intended behavior, or a bug in mod_jk, or
even a bug in Apache, but something seems amiss. Thoughts?
Your patch won't work.
No, not for this larger issue.
The real problem is in the
On Nov 2, 2007, at 12:18 AM, Mladen Turk wrote:
Ian Ward Comfort wrote:
I don't know if this is intended behavior, or a bug in mod_jk, or
even a bug in Apache, but something seems amiss. Thoughts?
Right, this is bug indeed.
If there is no Jk... directives the vhost conf is wrongly
Mladen Turk schrieb:
Rainer Jung wrote:
Hi,
be careful:
OK :)
I also added an option JkMountCopyAll,
OK, but clone is called when there is no JkMountCopy All defined
if (sconf sconf-was_initialized == JK_TRUE jk_mount_copy_all ==
JK_FALSE) {
clone_jk_config
So if there is
Ian Ward Comfort wrote:
clone_jk_config is bogus, and doesn't behave like it should
(copy only the basic data and no mounts)
Was this function introduced since 1.2.25?
Yes, I was talking about trunk not 1.2.25
Regards,
Mladen
On Nov 1, 2007, at 8:14 PM, Ian Ward Comfort wrote:
Here's one attempt at a patch, which fixes the problem in my
limited testing. It modifies the code path as little as possible,
since all I know about the intended behavior is what I've gleaned
from a cursory audit.
In working on this
