cachepolicy¶
Configuration for Integrated Cache policy resource.
Properties¶
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
policyname | <String> | Read-write | Name for the policy. Must begin with an ASCII alphabetic or underscore (_) character, and must contain only ASCII alphanumeric, underscore, hash (#), period (.), space, colon (:), at (@), equals (=), and hyphen (-) characters. Can be changed after the policy is created.
Minimum length = 1 |
rule | <String> | Read-write | Expression against which the traffic is evaluated.
The following requirements apply only to the Citrix ADC CLI: * If the expression includes one or more spaces, enclose the entire expression in double quotation marks. * If the expression itself includes double quotation marks, escape the quotations by using the \ character. * Alternatively, you can use single quotation marks to enclose the rule, in which case you do not have to escape the double quotation marks. |
action | <String> | Read-write | Action to apply to content that matches the policy.
* CACHE or MAY_CACHE action - positive cachability policy * NOCACHE or MAY_NOCACHE action - negative cachability policy * INVAL action - Dynamic Invalidation Policy. Possible values = CACHE, NOCACHE, MAY_CACHE, MAY_NOCACHE, INVAL |
storeingroup | <String> | Read-write | Name of the content group in which to store the object when the final result of policy evaluation is CACHE. The content group must exist before being mentioned here. Use the "show cache contentgroup" command to view the list of existing content groups.
Minimum length = 1 |
invalgroups | <String[]> | Read-write | Content group(s) to be invalidated when the INVAL action is applied. Maximum number of content groups that can be specified is 16.
Minimum length = 1 |
invalobjects | <String[]> | Read-write | Content groups(s) in which the objects will be invalidated if the action is INVAL.
Minimum length = 1 |
undefaction | <String> | Read-write | Action to be performed when the result of rule evaluation is undefined.
Possible values = NOCACHE, RESET |
newname | <String> | Read-write | New name for the cache policy. Must begin with an ASCII alphabetic or underscore (_) character, and must contain only ASCII alphanumeric, underscore, hash (#), period (.), space, colon (:), at (@), equals (=), and hyphen (-) characters.
Minimum length = 1 |
hits | <Double> | Read-only | Hits. |
undefhits | <Double> | Read-only | Number of Undef hits. |
flags | <Double> | Read-only | Flag. |
builtin | <String[]> | Read-only | .
Possible values = MODIFIABLE, DELETABLE, IMMUTABLE, PARTITION_ALL |
feature | <String> | Read-only | The feature to be checked while applying this config. |
__count | <Double> | Read-only | count parameter |
Operations¶
(click to see Properties )
- ADD
- DELETE
- UPDATE
- UNSET
- GET (ALL)
- GET
- COUNT
- RENAME
Some options that you can use for each operations:
Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:
http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes
If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.
Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,
To do this, you must specify the username and password in the request header of the NITRO request as follows:
X-NITRO-USER: <username>
X-NITRO-PASS: <password>
Note: In such cases, make sure that the request header DOES not include the following:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Note:
Mandatory parameters are marked in red and placeholder content is marked in green
add¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy
HTTP Method: POST
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Content-Type:application/json
Request Payload:
{"cachepolicy":{
<b> "policyname":<String_value>,
</b><b> "rule":<String_value>,
</b><b> "action":<String_value>,
</b> "storeingroup":<String_value>,
"invalgroups":<String[]_value>,
"invalobjects":<String[]_value>,
"undefaction":<String_value>
}}
Response:
HTTP Status Code on Success: 201 Created
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
delete¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy/ policyname_value<String>
HTTP Method: DELETE
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
update¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy
HTTP Method: PUT
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Content-Type:application/json
Request Payload:
{"cachepolicy":{
<b> "policyname":<String_value>,
</b> "rule":<String_value>,
"action":<String_value>,
"storeingroup":<String_value>,
"invalgroups":<String[]_value>,
"invalobjects":<String[]_value>,
"undefaction":<String_value>
}}
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
unset¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? action=unset
HTTP Method: POST
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Content-Type:application/json
Request Payload:
{"cachepolicy":{
<b> "policyname":<String_value>,
</b> "storeingroup":true,
"invalgroups":true,
"invalobjects":true,
"undefaction":true
}}
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
rename¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? action=rename
HTTP Method: POST
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Content-Type:application/json
Request Payload:
{"cachepolicy":{
<b> "policyname":<String_value>,
</b><b> "newname":<String_value>
</b>}}
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
get (all)¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy
Query-parameters:
attrs
http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? attrs=property-name1,property-name2
Use this query parameter to specify the resource details that you want to retrieve.
filter
http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? filter=property-name1:property-val1,property-name2:property-val2
Use this query-parameter to get the filtered set of cachepolicy resources configured on NetScaler.Filtering can be done on any of the properties of the resource.
view
http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? view=summary
Use this query-parameter to get the summary output of cachepolicy resources configured on NetScaler.
Note: By default, the retrieved results are displayed in detail view (?view=detail).
pagination
http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? pagesize=#no;pageno=#no
Use this query-parameter to get the cachepolicy resources in chunks.
HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{ "cachepolicy": [ {
"policyname":<String_value>,
"rule":<String_value>,
"action":<String_value>,
"storeingroup":<String_value>,
"invalgroups":<String[]_value>,
"invalobjects":<String[]_value>,
"hits":<Double_value>,
"undefaction":<String_value>,
"undefhits":<Double_value>,
"flags":<Double_value>,
"precededefrules":<String_value>,
"builtin":<String[]_value>,
"feature":<String_value>
}]}
get¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy/ policyname_value<String>
Query-parameters:
attrs
http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy/ policyname_value<String> ? attrs=property-name1,property-name2
Use this query parameter to specify the resource details that you want to retrieve.
view
http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy/ policyname_value<String> ? view=summary
Use this query-parameter to get the summary output of cachepolicy resources configured on NetScaler.
Note: By default, the retrieved results are displayed in detail view (?view=detail).
HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{ "cachepolicy": [ {
"policyname":<String_value>,
"rule":<String_value>,
"action":<String_value>,
"storeingroup":<String_value>,
"invalgroups":<String[]_value>,
"invalobjects":<String[]_value>,
"hits":<Double_value>,
"undefaction":<String_value>,
"undefhits":<Double_value>,
"flags":<Double_value>,
"precededefrules":<String_value>,
"builtin":<String[]_value>,
"feature":<String_value>
}]}
count¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/cachepolicy? count=yes
HTTP Method: GET
Request Headers:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
Accept:application/json
Response:
HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error
Response Header:
Content-Type:application/json
Response Payload:
{ "cachepolicy": [ { "__count": "#no"} ] }