Listing Popular Requests Oracle Fusion Middleware Online Documentation Library

Using Diagnostic Features 8-7 – Yes, by Surrogate-Control header: Compressed or not compressed because of the setting of the compress control directive in the Surrogate-Control response header. – Yes, by caching rule: Compressed or not compressed because the object matched a caching rule that enabled or disabled compression. – No, by MIME type: Not compressed because the objects MIME content type. – No, by default setting: Compression is enabled for the site and the browser accepts GZIP compressed responses, but there is no matching caching rule and the response does not contain a compress control header in the Surrogate-Control response header or a MIME type. See Section 1.2.5 to better understand when Oracle Web Cache automatically disables compression. – No, by Surrogate-Control header: Not compressed because of the setting of the compress control directive in the Surrogate-Control response header. – No, limited browser support: Not compressed because the clients browser has bugs and cannot handle receiving compressed objects. – No, needs Web Cache processing: Not compressed because the object requires parsing and tag process. For example, objects containing ESI tag requiring processing before there can be any cache hits. – No, browser capability: Not compressed because the clients browser did not indicate to Oracle Web Cache that it could accept GZIP compressed responses. Therefore, Oracle Web Cache does not compress any responses sent to this browser. – No, disabled for site: Not compressed because compression was disabled for the entire site. Section 2.11.3 to enable compression for a site. – No, object too small: Not compressed because the object was less than 23 bytes for compression to be beneficial. – No, routing only mode: Not compressed because the ROUTINGONLY attribute is set to YES in the webcache.xml file. See Section 3.8 for further information about this attribute.

8.7 Listing Cache Contents to a File

To generate a list of the URLs of all of the objects currently stored in the cache to a file named webache_contents.txt: 1. Navigate to the Web Cache Home page in Fusion Middleware Control. See Section 2.6.2 .

2. From the Web Cache menu, select Monitoring and then Popular Requests.

The Popular Request page displays.

3. From the Filter Popular Request By list, select an option:

– All : Select to display all requests received by the cache. – Cache Popular Requests : Select to display only those requests stored in the cache. 8-8 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache – Non Cache Popular Requests : Select to display only those requests not stored in the cache.

4. In Number of Popular Requests, enter the maximum number of URLs you want

displayed.

5. Click Export File.

6. In the message dialog, click OK to export the contents.

Oracle Web Cache writes the list of URLs to webcache_contents.txt in this directories: UNIX ORACLE_INSTANCEdiagnosticslogsWebCachewebcache_name Windows ORACLE_INSTANCE\diagnostics\logs\WebCache\webcache_name Each time you generate the list, Oracle Web Cache appends the data to the existing file. It lists the date that the data was appended to the file, followed by the URLs of the objects currently cached. The following example shows an excerpt of the webcache_ contents.txt file: Cache Contents at Wed Oct 20 11:47:03 2008 www.company.com:80imageslnavlnav_products.gif www.company.com:80imagesrnavrnav_red_line_1.gif www.company.com:80imagesbullets_and_symbolsblk_line_bullet_10.gif . . . Cache Contents at Wed Oct 25 13:01:24 2008 www.company.com:80imageswhite_spacer_xp.gif www.company.com:80imageswhite_spacer.gif www.company.com:80imagesminiappsnet.gif . . .

8.8 Configuring Where to Display Diagnostic Information

To understand how Oracle Web Cache can add diagnostic information to the Server response-header field or as a textual string in the HTML response body of an object, see Section 8.3 . To configure diagnostic information in the Server response-header field or the HTML response body:

1. From Oracle Web Cache Manager, in the navigator frame, select Logging and

Diagnostics Diagnostics. See Section 2.7.2 .

2. From the Cache-Specific Page Body Diagnostics table, select a cache, and then

click Enable to display diagnostic information in the HTML response body or Disable to disable the display of diagnostic information in the HTML response body. 3. To set diagnostic settings for the HTML response body:

a. From the Global Page Body Diagnostics Configuration table, click Edit.

The Edit Global Page Body Diagnostics Configuration dialog box displays.

b. In the URL Flag field, enter the string to append to the URL of the object.

By default, the string is set to +wcdebug. Using Diagnostic Features 8-9

c. In the Display Event Log Entries for Request field, select Yes to display

diagnostic information and TRACE event log entries in the HTML response body, or select No to only display diagnostic information.

d. Click Submit.

4. To enable or disable diagnostic settings in the Server response header, from the Global Server Header Diagnostics table, click Enable or Disable. 5. Click Apply Changes.