In the Cookie Name field, enter the name of the cookie.

6-18 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache

3. In the URL Parameters to Ignore field, specify the site-specific parameters.

Separate multiple parameters by commas or blank spaces.

4. Click Submit.

5. Click Apply Changes.

6. Restart Oracle Web Cache. See Section 2.13 . 7. Create a site-specific caching rule. See Section 6.8.1

6.8.4 Recognizing Similar Browser Types for Multiple-Version Objects Containing HTTP Request Headers

By default, Oracle Web Cache does not interpret the values of the HTTP request headers. When the Multiple Objects with the Same Selector by Other Headers for the User-Agent request-header field is selected in Fusion Middleware Control and the value of the User-Agent request header of the same URL differ, then Oracle Web Cache caches both pages separately. For example, if one request sends an HTTP request header of User-Agent: Mozilla4.0 compatible; MSIE 5.5; Windows and another request sends an HTTP request header of User-Agent: Mozilla4.0 compatible; MSIE 5.0; Windows; DigExt for different versions of Internet Explorer, Oracle Web Cache caches two separate pages. You can override this default behavior by configuring Oracle Web Cache with a User-Agent pattern string for a particular client. For the affected multiple-version objects, Oracle Web Cache adds an x-Oracle-Mapped-User request-header field, and uses the value of the string rather than the entire User-Agent value: x-Oracle-Mapped-User: MAPPEDUSERAGENT_String To configure Oracle Web Cache to cache and serve the same page for each browser type: 1. Create a caching rule for the pages that support the User-Agent request header, as described in Section 6.8.2 , ensuring you select the User-Agent header. 2. Use a text editor to open webcache.xml, located in: UNIX ORACLE_INSTANCEinstance_nameconfigWebCachewebcache_name Windows ORACLE_INSTANCE\instance_name\config\WebCache\webcache_name 3. Locate the GLOBALCACHINGRULES element. 4. For each browser type, add the following subelements in the next line after the GLOBALCACHINGRULES element: USERAGENTREMAPRULE MATCHSTRING=browser MAPPEDUSERAGENT=x-Oracle-Mapped-User-Agent_value MAPTYPE=USERAGENT If you enter multiple entries, order them according to how you want Oracle Web Cache to match. The order of these rules work in the same fashion as priority works for caching rules. Table 6–5 describes how to enter values for the subelements.