Changing web cache settings WAN optimization and web caching
FortiGate Version 4.0 Administration Guide
640 01-400-89802-20090424
http://docs.fortinet.com/ • Feedback
Cache Expired
Objects
Applies only to type-1 objects. When Cache Expired Objects is enabled,
type-1 objects that are already expired at the time of acquisition are cached
(if all other conditions make the object cacheable). When this setting is
disabled, already expired type-1 objects become non-cacheable at the time
of acquisition.
Revalidated Pragma-
no-cache
The pragma-no-cache (PNC) header in a client's request can affect the
efficiency of the FortiGate unit from a bandwidth gain perspective. If you do
not want to completely ignore PNC in client requests (which you can do by
using the ignore PNC option configuration), you can lower the impact of the
PNC by enabling the revalidate-pragma-no-cache setting. When the
revalidate-pragma-no-cache setting is enabled, a client's non-conditional
PNC-GET request results in a conditional GET request sent to the OCS if the
object is already in the cache. This gives the OCS a chance to return the 304
Not Modified response, consuming less server-side bandwidth, because it
has not been forced to return full content even though the contents have not
actually changed. By default, the revalidate PNC configuration is disabled
and is not affected by changes in the top-level profile. When the Substitute
Get for PNC configuration is enabled, the revalidate PNC configuration has
no effect.
Most download managers make byte-range requests with a PNC header. To
serve such requests from the cache, the revalidate pragma-no-cache option
should be configured along with byte-range support.
To Next Page
Loading...