Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Content Gateway Configuration Files > records.config > Cache control
Cache control
Help | Content Gateway | v8.5.x
 
Configuration Variable
Data Type
Description
proxy.config.http.cache.http
INT
Default: 1
Enables (1) or disables (0) caching of HTTP requests.
proxy.config.http.cache.ftp
INT
Default: 1
Enables (1) or disables (0) caching of FTP requests sent via HTTP.
proxy.config.http.cache.ignore_client_no_cache
INT
Default: 0
When enabled (1), Content Gateway ignores client requests to bypass the cache.
proxy.config.http.cache.ims_on_client_no_cache
INT
Default: 0
When enabled (1), Content Gateway issues a conditional request to the origin server if an incoming request has a no-cache header.
proxy.config.http.cache.ignore_server_no_cache
INT
Default: 0
When enabled (1), Content Gateway ignores origin server requests to bypass the cache.
proxy.config.http.cache.cache_responses_to_cookies
INT
Default: 3
How cookies are cached:
*
0 = do not cache any responses to cookies
*
1 = cache for any content-type
*
2 = cache only for image types
*
3 = cache for all but text content-types
proxy.config.http.cache.ignore_authentication
INT
Default: 0
When enabled (1), Content Gateway ignores WWW-Authentication headers in responses. WWW-Authentication headers are removed and not cached.
proxy.config.http.cache.cache_urls_that_look_dynamic
INT
Default: 0
Enables (1) or disables (0) caching of URLs that look dynamic.
proxy.config.http.cache.enable_default_vary_headers
INT
Default: 0
Enables (1) or disables (0) caching of alternate versions of HTTP objects that do not contain the Vary header.
proxy.config.http.cache.when_to_revalidate
INT
Default: 0
When to revalidate content:
*
0 = Use cache directives or heuristic (the default value).
*
1 = Stale if heuristic.
*
2 = Always stale (always revalidate).
*
3 = Never stale.
*
4 = Use cache directives or heuristic (0) unless the request has an If-Modified-Since header. If the request has an If-Modified-Since header, Content Gateway always revalidates the cached content and uses the client's If-Modified-Since header for the proxy request.
proxy.config.http.cache.when_to_add_no_cache_to_msie_requests
INT
Default: 0
When to add no-cache directives to Microsoft Internet Explorer requests. You can specify the following:
*
0 = no-cache not added to MSIE requests.
*
1 = no-cache added to IMS MSIE requests.
*
2 = no-cache added to all MSIE requests.
proxy.config.http.cache.required_headers
INT
Default: 0
The type of headers required in a request for the request to be cacheable.
*
0 = no required headers to make document cacheable.
*
1 = at least Last-Modified header required.
*
2 = explicit lifetime required, Expires or Cache-Control.
proxy.config.http.cache.max_stale_age
INT
Default: 604800
The maximum age allowed for a stale response before it cannot be cached.
proxy.config.http.cache.range.lookup
INT
Default: 1
When enabled (1), Content Gateway looks up range requests in the cache.
proxy.config.http.cache.cache_301_responses
INT
Default: 0
Enables (1) or disables (0) caching of "301" response pages.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Content Gateway Configuration Files > records.config > Cache control
Copyright 2023 Forcepoint. All rights reserved.