3. Caching


Prev	Chapter 4. Application Delivery Controller (ADC)	Next

3.1. Static Caching

Documents that can be cached, are locally stored by Web Security Manager. Any further requests for documents found in the cache, are automatically delivered to clients directly from Web Security Manager. Therefore, the back-end web servers can focus on delivering dynamic content with improved response times to clients, without the overhead of delivering static content like images, PDF documents, static HTML documents, style-sheets and others.

Enable static content caching Check box	If enabled, Web Security Manager will store static content from the web-server locally on Web Security Manager. This dramatically accelerates response times and off-loads the web-server. Default: `<enabled>`
Default caching action Input field	Web Security Manager can either cache all responses unless explicit no-cache instructions are set by the backend server or only cache content with response headers that indicates that the response is cache-able. Cache unless specifically instructed not to Cache all responses but honor Expires, Cache-Control: no-cache, private and no-store headers. Do not cache unless headers indicate content is cacheable Only cache responses if headers Expires, Cache-Control or Last-Modified indicates that the content is cache-able.
Inactive remove threshold Input field	Defines how long to keep data that is not requested in the cache. Valid input Number (seconds) Default value `3600`
Default caching time Input field	Define by response code how long to store cached responses in cache if expiration is not set by backend server. Valid input List of error codes and seconds. Default value `200 302 301 = 3600` `404 = 600` `any = 10` (any error code not specified directly).

	Warning
	Caching of content should only be activated where appropriate as caching, in particular of dynamic content, involves the risk of losing confidentiality to private data.

3.2. Dynamic caching

Using this option is only appropriate where the dynamically served content has the characteristics of static content. An example of such data could be news articles generated from a database.

If appropriate the effect of dynamic content caching can be dramatic. If for instance an article on a news site is requested at a rate of 100 requests/sec enabling caching with a content expiry of 20 seconds will result in 1 in every 2000 requests reaching the web server. The remaining 1999 will be served from the Web Security Manager cache.

Enable dynamic content caching

Check box

If enabled, Web Security Manager will store dynamic content from the web-server locally on Web Security Manager for a configurable number of seconds.

Default: <disabled>

Dynamic content expiry

Input field

Store dynamically cached documents for the specified period.

Valid input: Number (seconds)
Default value: 60

Caching locations

Cache response from requests matching regular expressions.

Enter regular expressions matching part of or the entire path part you want to be cached.

The expressions are matching from left to right. Full match is not implied but matching always start at start of line. This implies that for instance the expression /news will match any URI starting with /news.

Valid input: A valid regular expression
Input example: /news/.+\.php cache responses from php scripts served from locations in and below the directory news.
Default value: none

	Warning
	Caching of content should only be activated where appropriate as caching, in particular of dynamic content, involves the risk of losing confidentiality to private data.

3.3. Lower button bar

Flush DYNAMIC cache	Delete the contents of the website proxy static document cache.
Flush STATIC cache	Delete the contents of the website proxy static document cache.
Default values	Revert to default values.
Save settings	Click Save settings to save settings.

Prev	Up	Next
2. Load balancing	Home	4. Acceleration