Using Database Triggers for Automated Invalidation Requests

7-28 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache separated by a comma ,. Optional synchronicity directives may appear before or after any directive. ■ A synchronicity directive consists of the keyword SYNCHRONOUS followed by an equal sign = followed by either the keyword ONor the keyword OFF. ■ An invalidation consists of either a URI or a multi-directive specification. ■ A URI directive consists of a URI option directive followed by an equal sign = followed by a quoted string. ■ A URI option directive consists of the keyword URI. ■ A multi-directive specification has two distinct formats: – an explicit directory – an implicit directory ■ The explicit directory format consists of a URI directory directive followed by zero or more search key directives with consecutive search keys separated by a semicolon ; delimiter. ■ The implicit directory format consists of 1 or more search keys with consecutive search keys separated by a semicolon ; delimiter. ■ A URI directory consists of a URI directory option directive followed by an equal sign = followed by a quoted string. ■ A URI directory option directive consists of the keyword URI_DIR. ■ A search key consists of a search key option directive followed by an equal sign = followed by a quoted string. ■ A search key option directive consists of the keyword S_KEY. ■ A quoted string contains either a URI or a search key. Case-sensitivity rules and allowable character sets for URI and search key strings are the same as for other invalidation functionality. ■ For fully qualified URIs, a valid scheme includes either http: or https:, and a valid host name for example, www.host1.com. ■ Port numbers, when specified, must be valid as well. When a URI does not contain a port number, Oracle Web Cache assumes a default port number of 80 for HTTP and 443 for HTTPS. For implicit URI directories, Oracle Web Cache determines the directory based on the site of the original request. Oracle Web Cache ensures that the resulting site definition matches the site definition associated with the original request. In other words, as a security precaution, Oracle Web Cache disallows cross-site invalidation. ■ Note that with site-to-server mappings involving wildcards, some requests may have no associated site definition. In this case, the principal of conservatism applies, and Oracle Web Cache disallows the response header invalidation.

7.8.1 Example Usage

The following sections provide examples of invalidation response headers. The examples are based on the fictional Web application for Harrys Hardware store with the Web site: http:www.HarrysHardware.com