OMi servers reply to application users by sending a base URL that is used to calculate the correct references in the HTML requested by the user. When a reverse proxy is used, OMi must be configured to return the reverse proxy base URL, instead of the OMi base URL, in the HTML with which it responds to the user.
If the reverse proxy is being used for data collectors only, configuration is required only on the data collectors and reverse proxy, and not on the OMi servers.
There are two proxy modes that control user access to OMi servers:
Generic Mode
This mode is used when you try to access the gateway server via the reverse proxy. Any URLs requested are rewritten and sent back with the virtual URL of the gateway server.
If you are working in this mode, each time an HTTP/S request causes the OMi application to calculate a base URL, the base URL is replaced with the value defined for either the Default Virtual Server URL or the Local Virtual Server URL (when defined).
Note that when using this mode, you must ensure that all OMi clients are accessing the OMi servers via the URL defined for the Default Virtual Server URL or the Local Virtual Server URL parameters.
Specific Mode
This mode should be used if you want to concurrently access OMi servers through specific reverse proxies and by direct access. Accessing the server directly means that you are bypassing the firewall and proxy because you are working within your intranet.
If you are working in this mode, each time an application user’s HTTP/S request causes OMi to calculate a base URL, the base URL is replaced with the value defined for either the Default Virtual Server URL or the Local Server URL (when defined), if the HTTP/S request came through one of the IP addresses defined for the HTTP or HTTPS Reverse Proxy IPs parameter. If the HTTP/S request did not come through one of these IP addresses, the base URL that OMi receives in the HTTP/S request is the base URL that is returned to the client.