From Oracle Web Cache Manager, in the navigator frame, select Origin Select the Undefined Sites row, and then click ShowEdit Selected.

2-30 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache

d. In the Edit dialog for the threshold, modify the value for the Duration field or

select Use Default to use the default value. For the keep-alive timeout, if you set the value to 0, the connection to the client is not kept open. In addition, Oracle Web Cache sends the following response-header field in the response: Connection: Close For more information about the value to enter, see Section 2.3.4 .

e. Select option Use for all caches in the cluster to apply the duration to all

caches; deselect the option to apply the change to current cache only.

f. Click Submit.

g. Click Apply Changes.

You can always revert to the default values. In the Network Timeouts page, click Use Defaults, and then click Apply Changes to apply changes.

2.11.6 Task 6: Configure Error Pages

For situations in which there is a network communication error, site busy error, or ESI esi:include error, applications serve error pages. Rather than burden the origin server with this task, you can configure these pages to be served from Oracle Web Cache. To configure Oracle Web Cache to serve error pages for a site:

1. Create error pages and place them in the following directory locations:

UNIX ORACLE_INSTANCEinstance_nameconfigWebCachewebcache_namefiles Windows ORACLE_INSTANCE\instance_name\config\WebCache\webcache_name\files The default settings are as follows: ■ For network errors, the default setting is set to network_error.html. This error page is served when there is a network problem while connecting, sending, or receiving a response from an origin server for a cache-miss request. ■ For site busy errors, the default setting is set to busy_error.html. This page is served when origin server capacity is reached. ■ For ESI default fragments, the default setting is set to esi_fragment_ error.txt. This page is served when Oracle Web Cache cannot fetch the src specified in an esi:include tag and the alt attribute, onerror attribute, or the try |attempt |except block are either not present or fail. For a production environment, modify the defaults or create entirely new error pages to be consistent with other error pages for the site.

2. From Oracle Web Cache Manager, in the navigator frame, select Origin Servers,

Sites, and Load Balancing Error Pages. The Error Pages page appears.

3. Select either Default Pages or a site name in the table, and then click Edit.

The Edit Error Pages dialog box appears.

4. In the Network Error Page field, enter the file name of the error page delivered for

network communication problems between Oracle Web Cache and the Web site.