Never, No Content Will Ever Be Cached??”If this option is chosen, the cache rule
stipulates that the content will never be cached, regardless of whether or not the
source and request header indicate to do so. This basically tells the cache rule to
never cache the content.
. If Source and Request Headers Indicate to Cache??”This setting (the default) relies
on the source and request headers of the object that is retrieved to determine
whether it is cached.
To continue with the process, do the following:
1. Select what type of cache content settings to utilize and click Next to continue.
2. Check whether SSL responses will be cached or not, or if a size limit to cached
objects will be configured.
3. Click Next to continue.
The subsequent dialog box, shown in Figure 8.7, allows for the core customization of
HTTP caching settings, such as whether to enable HTTP caching, and what the content??™s
default TTL is. If a longer TTL is set, objects remain in the cache for longer periods of
time, although the risk that they will become stale becomes larger. If the TTL is shortened,
objects returned are less likely to be stale, but the server has to update the records
more often, increasing the amount of bandwidth required.
Pages:
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380