Currently you access these services from https://<yourthinlincserver>:<port> and don't have any option if you would like to run these services in a subdirectory. Example:
This could be achieved by either a configuration parameter or by having the services figure out their prefix path and then using relative paths in the code.
This scenario only happens with a proxy, so we don't need to have explicit support for this in ThinLinc. We just need to make sure we don't break the proxy's rewriting of URLs. If we start using relative URLs everywhere then things should be fine without any extra logic.
*** Bug 5678 has been marked as a duplicate of this bug. ***
It's actually possible to get this working, but it requires a lot of configuration in the proxy to rewrite all the URLs correctly. And these are internal aspects of ThinLinc so they are difficult for the administrator to keep an eye on.
Here is one guide a user has written to do this:
The biggest issue is the redirection from the master to the agent. Relative URLs are not possible there, since we are redirecting to a different host.