On Tue, Oct 18, 2016 at 8:36 AM, André Warnier (tomcat) <a...@ice-sa.com>
> On 18.10.2016 13:03, Mark Juszczec wrote:
>> No, the following line:
>> JkOptions +ForwardKeySize +ForwardURIEscaped -ForwardDirectories
>> is in an Apache conf file, but not in a VirtualHost entry.
>> Can this directive go in multiple places?
> See here : http://tomcat.apache.org/connectors-doc/reference/apache.html
> JkOptions are generally inherited by the <VirtualHost> sections, from the
> "main" (or "default") Apache configuration (aka outside <VirtualHost>
> But there are exceptions and additional rules, so check carefully.
Ok. My JkOptions directive appears outside the <VirtualHost> entry so I'm
going to assume its being inherited.
I will experiment with placing it in the <VirtualHost> section to see what
One quick question, do you or anyone reading know if something special
needs to be done to force % encoding when you have a workers.properties
My workers.properties contains the following:
worker.list= someWorker, lbAjpWorker,
In my conf file, someone has tied them together as follows:
LoadModule jk_module /somepath/modules/mod_jk.so
JkOptions +ForwardKeySize +ForwardURIEscaped -ForwardDirectories
JkMount /myService/* lbAjpWorker
JkMount /myService lbAjpWorker
I don't see anything that says "make sure everything going to lbAjpWorker
is % encoded"
Is the JkOptions appearing outside <VirtualHost *:9001> supposed to take
care of that?