It turned out to be a filter at web.xml of tomcat... Removing it the site is loading fine.
On Sun, Dec 22, 2019 at 2:17 AM Alex K <rightkickt...@gmail.com> wrote: > Hi all, > > I have a simple reverse proxy setup with the following lines: > > ProxyRequests Off > ProxyPreserveHost On > ProxyPass /iforms/ http://localhost:8443/app/ > ProxyPassReverse /iforms/ http://localhost:8443/app/ > > and relevant modules loaded: > proxy_module (shared) > proxy_balancer_module (shared) > proxy_http_module (shared) > > I am running apache 2.4. Apache does host other pages also. One of the > pages does provide access to the tomcat content. Apache is configured with > HTTPS while the tomcat content is loaded with reverse proxy (tomcat is not > configured with SSL) > > While it seems that apache tries to load the page (as it briefly shows the > loading bar of the tomcat app) it stops and the page remains blank. > > Apache does log the following which indicates a possible permission issue > for POST (?): > Apache access log: > > 192.168.28.100 - - [21/Dec/2019:23:57:29 +0000] "POST > /iforms/?v-1576972648967 HTTP/1.1" 403 414 " > https://localhost:11000/iforms/"; "Mozilla/5.0 (Windows NT 1 > > While tomcat does log the same 403 code: > Tomcat log: > 127.0.0.1 - - [21/Dec/2019:23:57:29 +0000] "POST /app/?v-1576972648967 > HTTP/1.1" 403 - > > Tomcat listens at port 8443. When accessing directly the app (and not > through reverse proxy of apache), the app loads fine ( > http://server:8443/app). > > Have checked apache configs for possible permissions issues without seeing > any issues. > > Would be grateful for any hints as I am checking this for more then 2 days > without being able to find out where the issue lies. > > Thanx, > Alex >
