Set up reverse proxy for HTTP Server (powered by Apache)

This topic provides information about how to set up a reverse proxy for your HTTP Server with the IBM^® Web Administration for i5/OS™ interface.

Important: Information for this topic supports the latest PTF levels for HTTP Server for i5/OS . It is recommended that you install the latest PTFs to upgrade to the latest level of the HTTP Server for i5/OS. Some of the topics documented here are not available prior to this update. See http://www.ibm.com/servers/eserver/iseries/software/http/services/service.htm for more information.

Configure your HTTP Server (powered by Apache) for reverse proxy using the IBM Web Administration for i5/OS interface. Only the tabs necessary to configure reverse proxy are discussed.

To configure your HTTP Server (powered by Apache) for reverse proxy, do the following:

1. Click the Manage tab.
2. Click the HTTP Servers subtab.
3. Select your HTTP Server (powered by Apache) from the Server list.
4. Select Global configuration from the Server area list.
   Note: If you want to configure a reverse proxy for a virtual host, click the virtual host from the Server area menu. See JKL Toy Company creates virtual hosts on HTTP Server (powered by Apache) for more information.
5. Expand Server Properties.
6. Click Proxy.
7. Click the Reverse Proxy tab in form.
8. Select Enabled from the Reverse proxy capabilities list.
9. Click Add under the Proxy request to remote servers table.
   Note: This table defines what requests will be mapped into the space of the server. The local server does not act as a proxy in the conventional sense, but appears as a mirror of the remote server.
10. Select Client requests from the Request Type list.

    When this option is used, non-proxy requests matching the URL specified in the Local virtual path column are transformed into proxy requests for the URL specified in the Remote server URL column. The proxy then handles the transformed request and returns any document (or error messages) the remote server provides. Clients remain unaware of any transformation.

11. Enter the local virtual path in the Local virtual path column.

    If a non-proxy requests matches the path specified in this column, the non-proxy request will be transformed into a proxy request for the URL specified in the Remote server URL column.

12. Select Specify URL from the list in the Remote server URL column.
13. Enter the remote server URL in the Remote server URL column.
14. Click Add under the Proxy requests to remote servers table.
15. Select Redirect requests from the Request Type list.

    When this option is used for redirected requests, headers in response documents are adjusted in the event that a "Redirect" is issued by the remote server. This allows clients to remain unaware of any transformation of the requests even if remote servers redirect the proxy.

16. Enter the path in the Local virtual path column.

    If your server is given a non-proxy request and the request matches the URL specified in the Local virtual path column, the URL request will be transformed into a proxy request for the URL specified in the Remote server URL column.

17. Enter the remote server URL in the Remoter server URL column.

    If a non-proxy request matches a URL in the Local virtual path column, the request will be transformed in the URL specified in the Remote server URL column. The client will be directed to the remote server URL without being aware of the redirect.

18. Click Continue.
19. Click OK.

All other options for reverse proxy are optional and allow you to modify specific reverse proxy capabilities.

After configuring your HTTP Server (powered by Apache) for reverse proxy, you can configure your server for a proxy chain.