Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 390)

374 Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
4
aging precedence <1-100> [<WORD>|ignore-case <WORD>] min-age <0-525600>
freshness-factor <0-100> max-age <0-525600>
{(override-expire|override-lastmod|
reload-into-ims)}
Parameters
aging precedence <1-100> [<WORD>|ignore-case <WORD>] min-age <0-525600>
freshness-factor <0-100> max-age <0-525600>
{(override-expire|override-lastmod|
reload-into-ims)}
Example
nx4500-5CFA2B(config-smart-cache-policy-test)#aging precedence 1 ignore-case
\\.jgp$ min-age 100 freshness-factor 75 max-age 200 reload-into-ims
nx4500-5CFA2B(config-smart-cache-policy-test)#
nx4500-5CFA2B(config-smart-cache-policy-test)#show context
smart-cache-policy test
aging precedence 1 ignore-case \\.jgp$ min-age 100 freshness-factor 75
max-age 200 reload-into-ims
access-log rotate 10 rotate-type duration 10 day
nx4500-5CFA2B(config-smart-cache-policy-test)#
aging precedence
<1-100> Configures content cache aging rules and assigns a precedence to each rule
•
precedence <1-100> – Specify a precedence for this aging rule.
<WORD> Specifies the regular expression to match. This option is case sensitive, and is the default setting.
ignore-case <WORD> Specifies the regular expression to match. This option is not case sensitive.
min-age <0-525600> Configures the minimum age, in minutes, of matched objects. This value specifies the lower limit on the
staleness of a response. A response is not considered stale unless its time in the cache exceeds the specified
minimum value.
•
<0-525600> – Specify a value from 0 - 525600 minutes. The default is 1 minute.
freshness-factor
<0-100> Configures the freshness factor of matched objects as a percentage value. Freshness is an expression of how
long Web content resides on the service platform’s local cache before being updated or removed.
•
<0-100> – Specify a value from 0 - 100%. The default is 100%.
max-age <0-525600> Configures the maximum age, in minutes, of matched objects. This value specifies the upper limit on the
freshness of a response. A response is not considered fresh unless its time in the cache is less than the
specified maximum value.
•
<0-525600> – Specify a value from 0 - 525600 minutes. The default is 525600.
(override-expire|
override-lastmod|
|reload-into-ims) Applies overrides. The options are:
•
override-expire – Optional. When selected, this option overrides the server sent explicit expiry time by the
configured minimum age value. This option causes the content cache engine to check the min value
before checking the Expires header. Thus, a non-zero min time makes the engine return an un-validated
cache hit even if the response is pre-expired.
•
override-lastmod – Optional. When selected, this option enforces minimum age even on objects that
were modified recently to force the minimum age period on recently modified cached content. This
option causes the content cache engine to check the min value before the LM-factor percentage.
•
reload-into-ims – Optional. When selected, this option makes the content cache engine to transform a
request with a no-cache directive into a validation (If-Modified-Since) request. In other words, the engine
adds an If-Modified-Since header to the request before forwarding. Note: This works only for objects that
have a Last-Modified timestamp. The outbound request retains the nocache directive, so that it reaches
the originating server.