I’m using a setup in which we use mod_proxy to proxy site requests to ‘www-.xxx.nl’ and cms requests to ‘cms-.xxx.nl’. We’re using BrXM 13 and have recently stumbled upon https://issues.onehippo.com/browse/HSTTWO-4534. So, moved forward to the latest hotfix 13.0.0.-1
Now, everything appears to work way better than before. However, I still see an unexpected request in my proxy access_logs, causing the SSO handshake to fail. I’m (reverse)proxypassing / to 127.0.0.1/cms. So everything that goes to 'cms-local.xxxx.nl/’ in my case goes to 127.0.0.1/cms/
The relevant request, yielding a 404 is:
brxm-local-httpd-proxy_1 | 127.0.0.1 - - [17/Apr/2019:06:44:03 +0000] “GET /cms/auth?destinationPath=/site/_cmsinternal/?org.hippoecm.hst.container.render_host=…&cmsCSID=… HTTP/1.1” 404 1094
The render_host has a correct value, but what surprises me is that there is an actual /cms/ in the received path. I’d expected /auth here and Tomcat also yields a 404 page in the browser indicating a request path of /cms/cms/auth.
So it seems this URL is not generated by BrXM in a proxy-aware fashion. Replaying this request and removing ‘/cms’ manually, yields a successful login. As a workaround, I can start writing rewriterules specifically for this request, but I’d rather have a confirmation on this being error behavior and/or how to fix it without workarounds.
Can anybody confirm this behavior?