Determining the URL Path

Managing Security and User Access 5-65 ■ HttpAbsoluteCgiPath : Defines the universal full dynamic root URL for the current Oracle Content Server instance. This is the path that executes the plug-in code in the web server that makes calls for dynamic content from the Oracle Content Server instance. It can have a different protocol or host name than the path in HttpBrowserFullCgiPath. For example, if the user specifies an IP address for the host name, the HttpBrowserFullCgiPath variable might pick up the IP address, but the HttpAbsoluteCgiPath variable would ignore it and use the appropriately internally configured host name. In the case of the browser path variables HttpBrowserFullCgiPath and HttpBrowserFullWebRoot, the implementation code determines what the user is currently using for protocol HTTP versus HTTPS, port number, and host name in the browser. It bases this determination on what the web server receives in its request.

5.9.2.3 Determining the URL Path

The BrowserUrlPath component supports the following configuration entries for guessing the URL path as the browser determines it: ■ HttpIgnoreWebServerInternalPortNumber : When set to true, this disables the use of the SERVER_PORT parameter. This entry is useful in a load balancing scenario where SERVER_PORT is not the port used by the browser, but is the port used by the load balancer to communicate with the web server. Enabling this entry will make it impossible without the BrowserUrlPath component for the Oracle Content Server instance to determine which port the browser used to access the web server. Without additional BrowserUrlPath configuration, this variable makes it impossible to both support an SSL and non-SSL address to the same Oracle Content Server instance. Using this variable prevents a load balancing configuration problem in which the load balancing server is using a different port number than the internal web server actually delivering the response to the request. ■ HttpIgnoreServerNameForHostName : When set to true, this disables the fallback logic where if the HTTP_HOST parameter is missing, the Oracle Content Server system will typically look for the parameter SERVER_NAME the web servers self identification. ■ HttpBrowserSSLPort : Only use this configuration entry if the SERVER_PORT entry is forwarded to the web server that communicates to the Oracle Content Server instance. This entry is used to decide whether a request is HTTPS or HTTP by comparing it with the SERVER_PORT parameter. The default SERVER_PORT value is 443. If you use HTTPS, but use a port other than 443, you must use this entry to set the expected HTTPS port number. ■ HttpBrowserUseIsSslCookie : If you want to look in the cookie to see if it indicates whether to use SSL or not, set this entry to true. ■ HttpBrowserIsSslCookieName : Only use this entry if the HttpBrowserUseIsSslCookie entry is enabled. Set the entry to the name of the cookie used to determine whether the server believes the browser is using SSL or not. The default is the cookie name UseSSL. The value of the cookie can be 1 or 0 zero. If a cookie with this name is present, then it will supersede other rules for determining whether to use SSL. ■ HttpBrowserUseHostAddressCookie : When set to true, this specifies to use a cookie to determine the full host name of the browser the part between the protocol and the relative web address. ■ HttpBrowserHostAddressCookieName : This entry is enabled only if HttpBrowserUseHostAddressCookie is enabled. Use this entry to specify the name 5-66 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server of the cookie used to determine what the server believes is the browsers current host name. The host name part of the protocol can include the port number. For example, HttpbrowserHostAddressCookieName=myhost:81 would specify the host myhost using the webport 81. If you do use this cookie, then it is unlikely that you need to enable HttpBrowserUseIsSslCookie, because if you use myhost:433, that will translate to https:myhostrest-of-url.

5.9.2.4 Changing Absolute Full Path Computation