Storage
The following table describes the storage options.
Option | Description | |
|
| |
Maximum | Specifies the maximum size of HTTP or FTP objects the | |
HTTP/FTP | appliance can cache. | |
object size in | Use a 0 (zero) to indicate no limit. | |
bytes | ||
| ||
|
| |
Maximum | Specifies the maximum number of HTTP alternates that the | |
number of | appliance can cache. | |
alternate | Use a 0 (zero) to indicate no limit. If a popular URL has | |
versions | ||
thousands of alternates, you might observe increased cache | ||
(HTTP) | ||
hit latencies (transaction times) as the appliance searches | ||
| ||
| through the alternates for each request. In particular, some | |
| URL addresses can have large numbers of alternates due to | |
| cookies. If the appliance is set to vary on cookies, you might | |
| encounter this problem. See Variable content‚ on page 38 for | |
| more information. | |
|
|
Freshness
The following table describes the freshness options.
Option | Description | |
|
| |
Verify | Configures the appliance to ask the original content server to | |
freshness | verify the freshness of objects according to the following list | |
by checking | before serving them. | |
| ❚ when the object has expired | |
| ❚ when the object has expired or if the object has no | |
| expiration date | |
| ❚ always | |
| ❚ never | |
|
| |
Minimum | Specifies the minimum freshness information required to | |
freshness | consider a document able to be cached: | |
information for | ❚ an explicit lifetime | |
a document to | ❚ a | |
be cached | ❚ nothing | |
| ||
|
| |
If an object | Specifies the time limits the appliance will keep an object in | |
has no | the cache: | |
expiration | ❚ minimum time in the cache. You can specify from | |
date | ||
15 minutes to two weeks. | ||
| ||
| ❚ maximum time in the cache. You can specify from | |
| 15 minutes to two weeks. | |
|
|
36Intel NetStructure Cache Appliance Administrator’s Guide
