Viewing Configuration Statistics Oracle Fusion Middleware Online Documentation Library

8-6 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache ■ Caching Reason : The reason that the object is cached or not cached. Possible values are: – ACL document: Cached or not cached because the object is an Access Control List ACL document for authorizing the access of a user to ACL-protected pages. – By caching rule: Cached or not cached because of a caching rule. – By ETag response header: Cached or not cached because of the ETag response header. – By HTTP headers: Cached or not cached because of information in the HTTP header. – By HTTP response code: Cached or not cached because of the HTTP response code. Normally any response code that is not 200 is not cached, but some non-200 responses can get cached because of a caching rule specifically allowing for it. – By reference TTL in ESI tag: Cached or not cached because of the nonzero value of the reference TTL time-to-live parameters specified in the ESI tag. – By Surrogate-Control response header: Cached or not cached because of information in the Surrogate-Control response header. – By X-Oracle-Cache response header: Cached or not cached because of information in the X-Oracle-Cache response header. – Cookie mismatch: Cached or not cached because the response contains a cookie that is not present in the request or that has a different value than the same cookie in the request. – No directive or rule: Cached or not cached because no directive or rule has stated that the object should be cached. – Not a GET or POST method: Not cached because the object was not a GET or POST method. – Object is too large: Not cached because the object is larger than the size specified as the Maximum Size of Single Cached Object specified in the Resource Limits and Timeout page. – POST body too large: Cached or not cached because the POST body was too large to be cached. – URL contains query string: Cached or not cached because the request contains a query string but the request did not match any caching rules. ■ Size : The column displays the size of the requested object. The size is represented in bytes, kilobytes KB, or megabytes MB. ■ Compressed?: This column displays the reason the object was compressed or not compressed: – Yes, by caching rule: Compressed because the object matched a caching rule that enabled or disabled compression. – Yes, by MIME type: Compressed because the objects MIME content type. – No, by default setting: Compression is enabled for the site and the browser accepts GZIP compressed response, 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. 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.