The Cache Page - HP P4535A - Web Cache Server Appliance Administrator's Manual

Appendix B

The Cache page

The following table describes the configuration options on the Cache page.
Option
Enable HTTP caching
Enable FTP caching
Enable NNTP caching
Ignore user requests to
bypass cache
Maximum HTTP/FTP
object size in bytes
Maximum number of
alternate versions
(HTTP)
View cache storage
configuration
Verify freshness by
checking
Minimum freshness
information for a
document to be
cacheable
If an object has no
expiration date
FTP cached objects
expire
Description
Cache Activation
Configures the Traffic Server to cache objects retrieved via HTTP.
Configures the Traffic Server to cache FTP objects retrieved via HTTP.
Configures the Traffic Server to cache objects retrieved via NNTP
If clients stipulate that their requests are not to be served from the cache, ignore
the stipulation (ignore client Cache Control:
Storage
Specifies the maximum size of HTTP or FTP objects to be cached.
If you enter (zero), there is no limit on the maximum HTTP or
CAUTION:
0
FTP object size.
Specifies the maximum number of HTTP alternates that Traffic Server can
cache.
CAUTION: If you enter (zero), there is no limit on the number of alternates
0
cached. If a popular URL has thousands of alternates, you might observe
increased cache hit latencies (transaction times) as Traffic Server searches over
the thousands of alternates for each request. In particular, some URLs can have
large numbers of alternates due to cookies. If Traffic Server is set to vary on
cookies, you might encounter this problem.
Click this link to see a list of the files or hard disk partitions allotted to cache
storage and their sizes.
NOTE: Raw partitions may not have an associated size.
Freshness
Configures the Traffic Server to ask the origin server to verify the freshness of
objects before serving them. Configures the Traffic Server to ask for
verification:
When the object has expired
When the object has expired or if the object has no expiration date
Always
Never
Specifies the minimum freshness information required to consider a document
cacheable:
An explicit lifetime
A last-modified time
Nothing
Some origin servers do not stamp the objects they serve with an expiration date,
but you can control how long these objects remain in the cache by specifying:
The minimum time they can remain in the cache (from 15 minutes to two
weeks).
The maximum time they can remain in the cache (from 15 minutes to two
weeks).
FTP objects carry no time stamp or date information and stay in the Traffic
Server cache pending removal on a schedule you specify (from 15 minutes to
two weeks).
Traffic Manager Configuration Options
headers).
no-cache
135