Jasper Ideas

Refer to case 01943135 for details.

Normally when we deploy JRS, it is a normal warfile accessible as:

https://<domain>/<contextRoot>

where the context root is jasperserver-pro (the warfile name).

We have a customer who wants to insert a context path into it, such as:

https://<domain>/<contextPath>/<contextRoot>

where the contextPath could have any number of slashes.

So the URL could look like: https://domain/a/context/path/jasperserver-pro

This is a normal Tomcat feature but it is failing for JRS where it works for other warfile deployments.

We need Tomcat to handle this because our customers may or may not have a load balancer, and in some cases there will be network dependencies will otherwise make this complicated.

Tomcat's documentation on this is here:
https://tomcat.apache.org/tomcat-9.0-doc/config/context.html

This seems like it should be a mandatory feature for a warfile delivery.