Using glide.proxy.path to put Self Hosted ServiceNow into a "subdirectory"?

[ralphbolton]

We are building a self-hosted Now platform. Installation has gone fine, and we're up to logging on as an admin.

However, we're planning to use more than one application on the same URL, so would like to "move" ServiceNow to a "subdirectory" in the URL space. For example:

Right now, it's accessed at https://app.example.com/ (here we see the Servicenow log on page, etc)

We'd like it to be https://app.example.com/servicenow/ (so that we can later have app.example.com/otherapp/ as well)

The glide.proxy.path property is listed throughout various install guides, but it always says to set this to /. We've tried setting it to /servicenow/, but it doesn't seem to do anything.

if it matters, our proxy is currently an nginx server on the same box as the now platform. We've tried two proxy configs, the first is to proxy_pass requests to http://locahost:16000/servicenow/ and the second was to proxy_pass requests to http://localhost:16000/ - neither seem to do work (the first option works a lot less well than the second!).

Given the scant documentation on the subject, is what we're trying to do even possible? If so, what did we miss that makes it work?

Any help much appreciated!

[jeffreyluto]

Did you find out an answer to that your question?  Our instance in Dev only has one JVM and directory  w/o an proxy or load balance so the glide.proxy.host = http://<insertdev_apphost>:16000

**But in QA and Prod we have a loadbalancer, no Haproxy, no SSL_mod in Apache nor Nginx we have the host as glide.proxy.host = https://<insertqa_apphost>:16000

glide.proxy.host = http://<insertqa_apphost>:16001

glide.proxy.host = http://<insertqa_apphost>:16002

glide.proxy.host = http://<insertqa_apphost>:16003

There is 1 thing regarding Parserver that does not work but every thing else does.

[jeffreyluto]

glide.proxy.path = /

Is what I mean to say

[ralphbolton]

No, no answer found. As far as I can tell, it's not possible - the config options are misleading. My guess is that it's a half-developed feature.

The only way I could find to do it was different hostnames in the URLs. The `glide_proxy.host` option tells the app how to generate URLs it puts into the HTML, but the `glide.proxy.path` option looks to be ignored (we set to to `/` as per the documentation, but I'm not even sure you need to specify it).

FWIW, it's rather a shame ServiceNow can't use the HTTP `Host` header to work out `glide.proxy.host`. That would make it possible to use the load balancer AND to be able to "go direct" to the port on the app server for testing purposes. Sadly, that too doesn't seem to be (properly) possible.