Click Create. Oracle Fusion Middleware Online Documentation Library

Configuring Security 5-11

5.4.3 Task 3: Configure SSL Settings for Oracle Web Cache Connections to Origin Servers

In this task, specify which SSL wallet to use for Oracle Web Cache connections to origin servers. This wallet must contain a certificate that matches the wallet used by the origin servers. To specify which SSL wallet to use for Web Cache connections to origin servers: 1. Navigate to the Web Cache Home page in Fusion Middleware Control. See Section 2.6.2 .

2. From the Web Cache menu, select Security and then SSL Configuration.

The SSL Configuration page displays.

3. Click the Expand icon next to the SSL Communication Between Web Cache and

Oracle HTTP Server section.

4. Click Change Wallet to display the Select Client Wallet dialog.

5. Select the wallet to use, and click OK. Ensure this wallet contains a certificate that

matches the wallet used by the origin server.

5.4.4 Task 4: Configure a Site to Require HTTPS Requests

If your environment has a mix of HTTP and HTTPS traffic, follow these instructions to restrict traffic for a specific site or URL prefix subset of the site, so that the requests must be received by Oracle Web Cache over SSL connections only. To configure the site settings, use a combination of Fusion Middleware Control and Oracle Web Cache Manager:

1. In the Fusion Middleware Control, specify a site definition and site-to-server

mapping, as described in Section 2.11.3 and Section 2.11.4 . When configuring the site definition, ensure you specify an HTTPS listening port. This site uses the wallet defined for that port.

2. From the Web Cache menu, select Availability Restart to save the configuration

settings and restart Oracle Web Cache.

3. From Oracle Web Cache Manager, in the navigator frame, select Properties Site

Definition . See Section 2.7.2 .

4. Select the site you created in Step 1, and click ShowEdit Site.

5. In the ShowEdit dialog, in the HTTPS Only Prefix field, enter the URL prefix for

which only HTTPS requests are served. If all traffic must be restricted to HTTPS, enter for the entire site.

6. Click Submit.

5.4.4.1 Modify ssl.conf for Keep-Alive Connections

By default, Oracle HTTP Server does not maintain keep-alive connection for HTTPS client requests from Microsoft Internet Explorer 5.5 and later releases. Internet Explorer has known issues with trying to reuse SSL connections after they have timed out. In order for Oracle HTTP Server to maintain keep-alive connections from Oracle Web Cache, you must remove the following entry from the ssl.conf file in ORACLE_HOMEApacheApacheconf directory on UNIX or ORACLE_ HOME \Apache\Apache\conf directory on Windows. SetEnvIf User-Agent .MSIE. nokeepalive ssl-unclean-shutdown