|Oracle® Fusion Middleware Administrator's Guide for Oracle Web Cache
11g Release 1 (11.1.1)
Part Number E10143-01
This preface introduces the new and changed administrative features of Oracle Web Cache that are described in this guide, and provides pointers to additional information.
11g Release 1 (11.1.1) includes many new features:
Request filtering: You can configure Oracle Web Cache with request filters to take actions on incoming requests based on certain attributes of the request. An incoming request must pass through configured request filters for a given site before Oracle Web Cache processes it. By configuring request filters, you can prevent malicious code from exploiting software vulnerabilities. For more information, see Chapter 4, "Configuring Request Filtering."
Invalidation using response headers: You can enable an origin server to invalidate cached content through an HTTP response header. For more information, see Section 7.4, "About Response Header Invalidations."
Request-based logging: Oracle Web Cache stores every request internally and then writes them in bulk after the request to the event logs. In this way, Oracle Web Cache groups all the requests For more information, see Section 9.1, "Introduction to Event Logs."
Oracle Diagnostic Logging (ODL) format for event logs: Oracle Web Cache supports the ODL format, which provides a common format for all diagnostic messages and log files. For more information, see Section 9.1, "Introduction to Event Logs."
Audit logging: Oracle Web Cache supports the Common Audit Framework for providing a uniform system for administering audits across Oracle Fusion Middleware components. The audit log files generated by Oracle Web Cache processes provide important information that can help you identify and diagnose potential security performance and configuration issues. For more information, see Oracle Fusion Middleware Security Guide.
Secure caching: You can configure Oracle Web Cache to support caching content that is secured by Oracle Single Sign-On authentication with no other authorization requirements. For more information, see Section 5.8, "Configuring Support for Caching Secured Content."