On Tue, Oct 18, 2016 at 8:36 AM, André Warnier (tomcat) <a...@ice-sa.com> wrote:
> 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 > -->Forwarding > > JkOptions are generally inherited by the <VirtualHost> sections, from the > "main" (or "default") Apache configuration (aka outside <VirtualHost> > entries). > 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 happens. 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 file? My workers.properties contains the following: worker.template.type=ajp13 worker.template.ping_mode=A worker.template.socket_timeout=30 worker.template.retries=2 worker.template.host=localhost worker.list= someWorker, lbAjpWorker, worker.lbAjpWorker.reference=worker.template worker.lbAjpWorker.port=8045 In my conf file, someone has tied them together as follows: LoadModule jk_module /somepath/modules/mod_jk.so JkOptions +ForwardKeySize +ForwardURIEscaped -ForwardDirectories <VirtualHost *:9001> DocumentRoot /some/dir/thatDoesNotExist/ JkEnvVar nameWithIntlChar JkMount /myService/* lbAjpWorker JkMount /myService lbAjpWorker </VirtualHost> 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?