Maybe it is just a question of perspective.
An Apache httpd VirtualHost is not a separate entity, like a child process or a
thread.
It is just a "personality" which any Apache child temporarily takes, during the processing
of one single request.
At the next request processed by this same Apache
My bad, if I put only
JkMount /jkmanager/* jkstatus
in the VirtualHost it works but it doesn't allow any other jk setting to be
put inside. So I have the rest of the mod_jk settings in the httpd.conf
making them globally available.
Still wonder why would only jkmanager behave this way?
Ig
