Specifications

Glossary
Glossary - 2
cacheable content expression
The cacheable content expression determines, based on evaluating variables
in the HTTP header of the request, whether a BIG-IP Cache Controller
directs a given request to a cache server or to an origin server. Any content
that does not meet the criteria in the cacheable content expression is deemed
non-cacheable.
cache pool
The cache pool specifies a pool of cache servers to which requests are
directed in a manner that optimizes cache performance. The BIG-IP Cache
Controller directs all requests bound for your origin server to this pool,
unless you have configured the hot content load balancing feature, and the
request is for hot (frequently requested) content. See also hot and origin
server.
chain
A chain is a series of filtering criteria used to restrict access to an IP address.
The order of the criteria in the chain determines how the filter is applied,
from the general criteria first, to the more detailed criteria at the end of the
chain.
content affinity
Content affinity ensures that a given subset of content remains associated
with a given cache server to the maximum extent possible, even when cache
servers become unavailable, or are added or removed. This feature also
maximizes efficient use of cache memory.
content converter gateway
A content converter gateway is a gateway for converting URLs to ARLs.
See also ARL.
content demand status
The content demand status is a measure of the frequency with which content
in a given hot content subset is requested over a given hit period. Content
demand status is either hot, in which case the number of requests for content
in the hot content subset during the most recent hit period has exceeded the
hot threshold, or cool, in which case the number of requests during the most
recent hit period is less than the cool threshold. See also cool, cool
threshold, hit period, hot, hot content subset, and hot threshold.
content hash size
Specifies the number of units, or hot content subsets, into which the content
is divided when determining whether content is hot or cool. The requests for
all content in a given subset are summed, and a state (hot or cool) is
assigned to each subset. The content hash size should be within the same
order of magnitude as the actual number of requests possible. For example,
if the entire site is composed of 500,000 pieces of content, a content hash
size of 100,000 is typical.