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 bug I discovered a discrepancy (or perhaps just a confusing ambiguity?) between mod_jk's behavior and its documentation regarding VirtualHosts.
The docs specify that the default for JkMountCopy is "off", that is, that JkMounts from a main server are by default not inherited by its child VirtualHosts. But this is only true if there are mod_jk directives within the VirtualHost container -- if there are no such directives, JkMounts are inherited and it is as if JkMountCopy were "on". The cause of this behavior is just what was underlying the JkEnvVar bug; namely that when a VirtualHost has no mod_jk directives then the server_rec objects for the main server and the virtual host share a single jk_server_conf_t object.
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?
-- Ian Ward Comfort <[EMAIL PROTECTED]> System Administrator, Student Computing, Stanford University --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
