From the Web Cache menu, select Administration and then Caching Rules.

6-14 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache Compress Select this option to instruct Oracle Web Cache to serve compressed cacheable and non-cacheable objects to browsers. To enable compression for this rule, you must also enable compression for the site. To set the compression property for a site, see Section 2.11.3 . Oracle Web Cache automatically disables compression for some common file types which are known to be already compressed. Oracle recommends not compressing content for these file type, including GIF, JPEG, and PNG images, or files that are already compressed with utilities like WinZip or GZIP. Compressing these files incurs additional overhead without gaining any compression benefit. See Section 1.2.5 to better understand when Oracle Web Cache automatically disables compression. Match URL By Select to base the match evaluation on the URL expression: 1. Select the expression type: - File Extension: Select to apply the caching rule to objects ending in a particular file extension, such as .gif. In the accompanying field, enter the file extension. Because Oracle Web Cache internally starts the file extension with a period ., it is not necessary to enter it. - Path Prefix: Select to apply the caching rule to objects matching a path prefix. In the accompanying field, enter the path prefix of the objects. Start the path with ; do not start the path with http:host_name:port. The prefix is interpreted literally, including reserved regular expression characters. These characters include periods ., question marks ?, asterisks , brackets [], curly braces {}, carets , dollar signs , and backslashes \. - Regular Expression: Select to apply the caching rule to objects matching regular expression syntax. In the accompanying field, enter the regular expression of the objects. Remember to use to denote the start of the URL and to denote the end of the URL. 2. Click the Case Insensitive Match check box to match requests regardless of the case. If you do not select this check box, the rule bases the match on the case. Table 6–4 Cont. Caching Rules - General Page Element Description Caching and Compressing Content 6-15 MIME Type Select to base the match evaluation on the Content-Type response header: 1. Select an operation value to determine where Oracle Web Cache searches for the expression value in the responses MIME type: -Equals: Select to instruct Oracle Web Cache to match the MIME type if it equals the expression. -Starts With: Select to instruct Oracle Web Cache to match the MIME type if it starts with the expression. -Contains: Select to instruct Oracle Web Cache to match the MIME type if it contains the expression. For most match evaluations, select the Starts with option, because the Content-Type response header typically has additional content parameter values. If you select Equals, then the match may not work as you expect. 2. In the accompanying field, enter the string value that you want Oracle Web Cache to compare against the responses MIME type. You can enter a list in the expression field, separated by commas. HTTP Methods Select one or more of the following HTTP request methods: ■ GET: An HTTP request method used for simple requests for Web pages. A GET method is made up of a URL. Requests for pages that use the GET methods are typically cached. ■ GET with query string: An HTTP request method made up of a URL and a query string containing parameters and values. ■ POST Body Expression: An HTTP request method used for requests that modify the contents of the data store on the application Web server, such as posting a message to a mailing list, submitting forms for registration purposes, or adding entries to the database. Note: If your Web sites GET with query string or POST methods are used for forms that make changes to the origin server or database, do not select GET with query string or POST Body Expression . Select these options only if the forms are used in search forms. Required Request Parameters Click Add to enter an embedded URL parameter or POST body parameter and its value in the corresponding Parameter Name and optional Value fields. Notes: ■ If you selected Regular Expression from the Match URL By list, you either use the Required Request Parameters section or manually enter the embedded URL parameters alphabetically in the accompanying Match URL By field. When you use the Required Request Parameters section, the embedded URL parameters are automatically sorted. See Section 6.8.1.1 for information about how to specify parameters in the accompanying Match URL By field. ■ If you selected POST in the HTTP Methods section and do not specify POST body parameters in this section, specify the HTTP POST body in the accompanying POST Body Expression field. To apply this rule to any POST request body, enter . in the field. Table 6–4 Cont. Caching Rules - General Page Element Description