gular NIA Don't Cache gular Eapression"for ten an ithN/A N/A Cache gular thN/ N/A Aff NA ET thN/A Cache GET lew. N/A Cache query Figure4:Sampledynamiccachingrulesforwww.oracle.com,asdisplayedintheWebCachemAnag administrative user interfac Examples of non-transactional pages that are dynamically generated include product catalogs, where information on pricing and inventory might vary from one moment to the next auction views, which must be regenerated after each successful bid is processed earch results, which can change as site content is added and removed portal pages, which display personalized content for each user Specifying caching policies is a declarative process. When an administrator assig caching rules, he specifies the regular expression for either a specific URL or a collection of URls and whether or not the content matching those URLs should be cached. Examples of content that administrators would typically declare non- cacheable include update transactions, personal account views, and so forth. In addition to the URl, administrators can specify optional selectors for more fine- grained caching rules These additional selectors include the Http request method (geT, Get with query string or Post)and, if Post is selected the Http poSt body of the documents If no caching rules are specified or if no rules match a particular request, then OracleAS Web Cache behaves just as traditional proxy caches do; that is, it relies on standard Http header information to determine what is cacheable Naive proxy caches typically only cache static content for reasons discussed earlier in this paper OracleAS Web Cache 10g(10.1.2)-Technical White Pap poration, All Rights ReservedPage 12 OracleAS Web Cache 10g (10.1.2) -- Technical White Paper Copyright © 1999-2005 Oracle Corporation, All Rights Reserved Figure 4: Sample dynamic caching rules for www.oracle.com, as displayed in the Web Cache Manager administrative user interface Examples of non-transactional pages that are dynamically generated include: • product catalogs, where information on pricing and inventory might vary from one moment to the next • auction views, which must be regenerated after each successful bid is processed • search results, which can change as site content is added and removed • portal pages, which display personalized content for each user Specifying caching policies is a declarative process. When an administrator assigns caching rules, he specifies the regular expression for either a specific URL or a collection of URLs and whether or not the content matching those URLs should be cached. Examples of content that administrators would typically declare non￾cacheable include update transactions, personal account views, and so forth. In addition to the URL, administrators can specify optional selectors for more fine￾grained caching rules. These additional selectors include the HTTP request method (GET, GET with query string, or POST) and, if POST is selected, the HTTP POST body of the documents. If no caching rules are specified or if no rules match a particular request, then OracleAS Web Cache behaves just as traditional proxy caches do; that is, it relies on standard HTTP header information to determine what is cacheable. Naïve proxy caches typically only cache static content for reasons discussed earlier in this paper