cache parameter¶
The following operations can be performed on "cache parameter":
set cache parameter¶
Modifies the global configuration of the integrated cache. You can modify the settings of various parameters.
Synopsys¶
set cache parameter [-memLimit <MBytes>] [-via <string>] [-verifyUsing <verifyUsing>] [-maxPostLen <positive_integer>] [-prefetchMaxPending <positive_integer>] [-enableBypass ( YES | NO )] [-undefAction ( NOCACHE | RESET )] [-enableHaObjPersist ( YES | NO )]
Arguments¶
memLimit
Amount of memory available for storing the cache objects. In practice, the amount of memory available for caching can be less than half the total memory of the Citrix ADC.
via
String to include in the Via header. A Via header is inserted into all responses served from a content group if its Insert Via flag is set.
verifyUsing
Criteria for deciding whether a cached object can be served for an incoming HTTP request. Available settings function as follows:
HOSTNAME - The URL, host name, and host port values in the incoming HTTP request header must match the cache policy. The IP address and the TCP port of the destination host are not evaluated. Do not use the HOSTNAME setting unless you are certain that no rogue client can access a rogue server through the cache.
HOSTNAME_AND_IP - The URL, host name, host port in the incoming HTTP request header, and the IP address and TCP port of
the destination server, must match the cache policy.
DNS - The URL, host name and host port in the incoming HTTP request, and the TCP port must match the cache policy. The host name is used for DNS lookup of the destination server's IP address, and is compared with the set of addresses returned by the DNS lookup.
Possible values: HOSTNAME, HOSTNAME_AND_IP, DNS
maxPostLen
Maximum number of POST body bytes to consider when evaluating parameters for a content group for which you have configured hit parameters and invalidation parameters.
Default value: 4096
Minimum value: 0
prefetchMaxPending
Maximum number of outstanding prefetches in the Integrated Cache.
Minimum value: 0
enableBypass
Evaluate the request-time policies before attempting hit selection. If set to NO, an incoming request for which a matching object is found in cache storage results in a response regardless of the policy configuration.
If the request matches a policy with a NOCACHE action, the request bypasses all cache processing.
This parameter does not affect processing of requests that match any invalidation policy.
Possible values: YES, NO
undefAction
Action to take when a policy cannot be evaluated.
Possible values: NOCACHE, RESET
enableHaObjPersist
The HA object persisting parameter. When this value is set to YES, cache objects can be synced to Secondary in a HA deployment. If set to NO, objects will never be synced to Secondary node.
Possible values: YES, NO
Default value: NO
unset cache parameter¶
Use this command to remove cache parameter settings.Refer to the set cache parameter command for meanings of the arguments.
Synopsys¶
unset cache parameter [-memLimit] [-via] [-verifyUsing] [-maxPostLen] [-prefetchMaxPending] [-enableBypass] [-undefAction] [-enableHaObjPersist]
show cache parameter¶
Displays the global configuration of the Integrated Cache.
Synopsys¶
show cache parameter
Outputs¶
diskLimit
The disk limit for the Integrated Cache.
maxDiskLimit
The maximum value of the memory limit for the Integrated Cache.
memLimit
The memory limit for the Integrated Cache.
memLimitActive
Active value of the memory limit for the Integrated Cache.
maxMemLimit
The maximum value of the memory limit for the Integrated Cache.
via
The string that is inserted in the "Via" header.
verifyUsing
The criteria for deciding whether a cached object can be served for an incoming HTTP request.
maxPostLen
The maximum POST body size that the IC can accumulate.
prefetchCur
Number of current outstanding prefetches in the IC.
prefetchMaxPending
The maximum number of outstanding prefetches on the content group.
enableBypass
When this value is set to NO, an incoming request will serve a hit if a matching object is found in cache storage, regardless of the cacheability policy configuration. If set to YES, the bound request cacheability policies are evaluated before attempting any hit selection in the cache storage. If the request matches a policy with a NOCACHE action, the request will bypass all cache processing. This flag does not affect processing of requests that match any invalidation policy.
undefAction
Action to take when a policy cannot be evaluated.
enableHaObjPersist
The HA object persisting parameter. When this value is set to YES, cache objects can be synced to Secondary in a HA deployment. If set to NO, objects will never be syned to Secondary node.