HTTP Cache Rules

The HTTP Cache Rules panel allows you to specify custom rules for caching content. Many web sites built on common CMS platforms prevent caching indiscriminately and many other sites specify no information about freshness of resources. HTTP cache rules allow you to provide some cacheability of resources in these cases.

Each rule you create allows you to set a number of criteria for how the rule is applied:

• Sites

  The site(s) that this rule applies to. A site is defined as the domain name portion of a URL (the portion of the URL preceding the resource string).

  For example a site could be defined as wingate.com. This site would then include all URLs that contained http://wingate.com (e.g. http://wingate.com/sales.htm, http://wingate.com/example.asp etc.).

• Content-Types

  The content type(s) that this rule applies to

• Action

  The action to take if the other criteria of the rule match

Read more about creating cache rules

Rule ordering

Whenever a response is being considered for caching WinGate will scan the list of rules looking for a match. As soon as a match is found, WinGate will apply that rule and stop checking other rules that follow in the list.

You can change the order in which the rules are evaluated by selecting the Move rule up or Move rule down options from the Tasks menu or right-clicking on an item and selecting the desired option from the popup menu.