On 30/09/2019 20:33, Rainer Jung wrote: > Thanks, eactly what we need. +1. I can reproduce this.
> I will look into it, but it might take two > or three days. Anyone who can do it more quickly is welcome. I suspect > these log lines point to the root cause: > >> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug] >> jk_servlet_normalize::jk_util.c (2184): URI on entering >> jk_servlet_normalize: [] >> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [emerg] >> jk_servlet_normalize::jk_util.c (2188): [] does not start with '/'. >> [Mon Sep 30 15:04:03 2019][3906:140148297873536] [debug] Also agreed. > but we'll need to investigate whether it can be fixed by configuration > or needs a code change. Our configs are pretty flexible but we need to > understand a bit better how we can let mod_jk keep out of the SSI > handling of the internal requests. > > As far as I have understood, you do not actually want these SSI requests > to be forwarded via mod_jk/AJP and instead want all of them being > handled directly by Apache? That is my understanding as well. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
