Enonic version: 6.13.1
We have a solution where we reroute a site to the root with VHOST (/no to /). We’ve also implemented a custom application to allow login via a Norwegian authentication service. As part of the login-experience we want to show some information from the original node that the user is trying to access. Now, as we use rerouting the path (and URL) is not aligned with the original node’s path (e.g. error.request.path will be /test, but original node path is /no/test).
Is there a way to infer the original path of the node without hardcoding?