Using Reverse Proxy Servers

This section provides an overview of reverse proxy servers and discusses how to:

  • Make reverse proxy settings.

  • Issue requests by using a proxy server.

  • Specify hosts that should not be proxied.

Image: Example of the reverse proxy architecture

A reverse proxy server accepts requests from client browsers on behalf of another web server and then relays those requests to the web server. The reverse proxy server checks web requests and responses to ensure that they adhere to network security policies. For example, a reverse proxy server validates that a command intended for the target web server is a valid command for that server. In this diagram, the HR web server,, is behind a reverse proxy server,


All internet requests for the HR web server are relayed by to The site URL routes the client to the proxy as if it were a web server. Replicated content is delivered from the proxy cache to the external client without exposing the origin server or the network residing safely behind the firewall. You can balance the load of an overtaxed web server by installing multiple instances of the web server.

Any external content must come from a node that's registered in the portal database so that the portal servlet can look up the node name based on the URL of the content. The external content HTML is rewritten to use that proxied format.

On the Web Profile - Virtual Addressing page, specify the reverse proxy server to use by entering it in the Reverse Proxy Server List grid. Include the protocol, the host name, the HTTP port, and the HTTPS port.

For you to make a portal issue requests by using a proxy server, the proxy server settings are controlled by these Java system properties:

  • http.proxyHost

  • http.proxyPort

  • https.proxyHost

  • https.proxyPort

To use a proxy server for the HTTP protocol, set these properties:


To use a proxy server for the HTTPS protocol, set these properties:


The properties must be passed to the Java interpreter as command-line directives.

Alter the setEnv.cmd or file located in WebLogic domain’s bin folder. Define the properties on the command line that starts the Java Virtual Machine like this:

set PROXY=-Dhttp.proxyHost=proxyhostname -Dhttp.proxyPort=proxy_port -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=proxy_port

Later add the preceding property in startPIA.cmd or in the Java command line that starts the WebLogic server domain.

%JAVA_HOME%\bin\java -ms64m -mx64m 
-classpath %JAVA_CLASSPATH% %PROXY% 
-Dweblogic.home=.\weblogic.policy weblogic.Server

goto finish

If your portal implementation retrieves content from both an intranet and the internet, you may have a problem retrieving both internal and external content if the proxy server is not aware of the address of the intranet content. You can pevent this situation by specifying that certain hosts (such as your intranet hosts) should not be accessed through the proxy server.

For Oracle WebLogic, specify the hosts not to be proxied in the HTTP_PROXY_NONPROXY_HTTPHOSTS and HTTP_PROXY_NONPROXY_HTTPSHOSTS environment variables with the setEnv.cmd ( in Unix) script. Refer to comments in setEnv for specific syntax.

You can list a set of patterns that should not be accessed through proxies, with each one separated by the pipe character ( | ). This example shows a setting that makes all HTTP connections to the eng domain bypass the proxy settings: