It may be desired to place Ops Manager behind a proxy or load balancer based on a URL path (aka sub-directory or prefix). For example, an nginx location may want to proxy pass connections to Ops Manager on "location /opsmanager"
Currently, the Ops Manager Base URL appears to only accept and use the scheme, hostname/domain, and port. Additional path details are ignored by redirects sourcing from javascript functions and html links/resources.

Current workarounds require a unique/dedicated server name for proxying or load balancing to Ops Manager web service(s).

This feature request is for supporting custom URL paths when using Ops Manager behind a proxy or similar network appliances.