Caching
The ADC Caching page includes the following sections. Click on the link to go to the corresponding section to learn more:
To go to the documentation for the previous section of ADC, see Load Balancing . To go to the documentation for next subsection in the ADC section, see Application Delivery Controller (ADC) Acceleration.
To access the Caching page in the WAF management interface:
- On the left panel, under Services, click Websites.
- On the Websites page, click the website you want to manage.
- Under ADC, click Caching.
To save configuration changes or edits you make to any features and options, you must click Save on the lower-right of the section or page where you are making changes. Click apply changes on the upper-left corner of the page, and then click OK. Your changes will not be stored if you do not properly save your changes.
Alert Logic Managed Web Application Firewall (WAF) locally stores documents that can be cached. Any further requests for documents found in the cache are automatically delivered to clients directly from WAF. 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.
Caching content must only be activated where appropriate as caching. In particular for dynamic content, which involves the risk of losing confidentiality to private data.
Enable static content caching
Checkbox |
If enabled, WAF stores static content from the web-server locally on WAF. This dramatically accelerates response times and off-loads the web-server. Default: |
Default caching action
Input field |
WAF can either cache all responses unless the backend server explicitly instructs no-cache or only cache content with response headers that indicate that the response is cache-able.
|
Inactive remove threshold
Input field |
Defines how long to keep data that is not requested in the cache.
|
Default caching time
Input field |
Response code defines how long to store cached responses in cache if backend serve does not set rexpiration.
|
Use this option only appropriate when the dynamically served content has the characteristics of static content. An example of this data can be news articles generated from a database.
If appropriate, the effect of dynamic content caching can be dramatic. For instance, if an article on a news site is requested at a rate of 100 requests/sec, enabling caching with a content expiry of 20 seconds results in 1 in every 2000 requests reaching the web server. The remaining 1999 is served from the WAF cache.
Caching content must only be activated where appropriate as caching. In particular for dynamic content, which involves the risk of losing confidentiality to private data.
Enable dynamic content caching
Check box |
If enabled, WAF store a dynamic content from the web server locally for a configurable number of seconds. Default: |
Dynamic content expiry
Input field |
Store dynamically cached documents for the specified period.
|
Caching locations |
Cache response from requests matching regular expressions. Enter regular expressions to match part of, or the entire path part you want cached. The expressions match from left to right. Full match is not implied, but matching always start at the beginning of line. For example, the expression
|
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 to save settings. |