Download full document:

cmpparameter

Configuration for CMP parameter resource.

Properties

(click to see Operations)

NameData TypePermissionsDescription
cmplevel<String>Read-writeSpecify a compression level. Available settings function as follows:
* Optimal - Corresponds to a gzip GZIP level of 5-7.
* Best speed - Corresponds to a gzip level of 1.
* Best compression - Corresponds to a gzip level of 9.
Default value: optimal
Possible values = optimal, bestspeed, bestcompression
quantumsize<Double>Read-writeMinimum quantum of data to be filled before compression begins.
Default value: 57344
Minimum value = 8
Maximum value = 63488
servercmp<String>Read-writeAllow the server to send compressed data to the Citrix ADC. With the default setting, the Citrix ADC appliance handles all compression.
Default value: ON
Possible values = ON, OFF
heurexpiry<String>Read-writeHeuristic basefile expiry.
Default value: OFF
Possible values = ON, OFF
heurexpirythres<Double>Read-writeThreshold compression ratio for heuristic basefile expiry, multiplied by 100. For example, to set the threshold ratio to 1.25, specify 125.
Default value: 100
Minimum value = 1
Maximum value = 1000
heurexpiryhistwt<Double>Read-writeFor heuristic basefile expiry, weightage to be given to historical delta compression ratio, specified as percentage. For example, to give 25% weightage to historical ratio (and therefore 75% weightage to the ratio for current delta compression transaction), specify 25.
Default value: 50
Minimum value = 1
Maximum value = 100
minressize<Double>Read-writeSmallest response size, in bytes, to be compressed.
cmpbypasspct<Double>Read-writeCitrix ADC CPU threshold after which compression is not performed. Range: 0 - 100.
Default value: 100
Minimum value = 0
Maximum value = 100
cmponpush<String>Read-writeCitrix ADC does not wait for the quantum to be filled before starting to compress data. Upon receipt of a packet with a PUSH flag, the appliance immediately begins compression of the accumulated packets.
Default value: DISABLED
Possible values = ENABLED, DISABLED
policytype<String>Read-writeType of policy. Available settings function as follows:
* Classic - Classic policies evaluate basic characteristics of traffic and other data.
* Advanced - Advanced policies (which have been renamed as default syntax policies) can perform the same type of evaluations as classic policies. They also enable you to analyze more data (for example, the body of an HTTP request) and to configure more operations in the policy rule (for example, transforming data in the body of a request into an HTTP header).
Possible values = CLASSIC, ADVANCED
addvaryheader<String>Read-writeControl insertion of the Vary header in HTTP responses compressed by Citrix ADC. Intermediate caches store different versions of the response for different values of the headers present in the Vary response header.
Default value: DISABLED
Possible values = ENABLED, DISABLED
varyheadervalue<String>Read-writeThe value of the HTTP Vary header for compressed responses. If this argument is not specified, a default value of "Accept-Encoding" will be used.
Minimum length = 1
externalcache<String>Read-writeEnable insertion of Cache-Control: private response directive to indicate response message is intended for a single user and must not be cached by a shared or proxy cache.
Default value: NO
Possible values = YES, NO
builtin<String[]>Read-onlyFlag to determine whether compression is default or not.
Possible values = MODIFIABLE, DELETABLE, IMMUTABLE, PARTITION_ALL

Operations

(click to see Properties)

UPDATE| UNSET| GET (ALL)

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 redand placeholder content is marked in <green>.

update

URL:http://<netscaler-ip-address>/nitro/v1/config/cmpparameter

HTTP Method:PUT

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Content-Type:application/json

Request Payload:

{"cmpparameter":{
"cmplevel":<String_value>,
"quantumsize":<Double_value>,
"servercmp":<String_value>,
"heurexpiry":<String_value>,
"heurexpirythres":<Double_value>,
"heurexpiryhistwt":<Double_value>,
"minressize":<Double_value>,
"cmpbypasspct":<Double_value>,
"cmponpush":<String_value>,
"policytype":<String_value>,
"addvaryheader":<String_value>,
"varyheadervalue":<String_value>,
"externalcache":<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/cmpparameter?action=unset

HTTP Method:POST

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Content-Type:application/json

Request Payload:

{"cmpparameter":{
"policytype":true,
"cmplevel":true,
"quantumsize":true,
"servercmp":true,
"heurexpiry":true,
"heurexpirythres":true,
"heurexpiryhistwt":true,
"minressize":true,
"cmpbypasspct":true,
"cmponpush":true,
"addvaryheader":true,
"varyheadervalue":true,
"externalcache":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

get (all)

URL:http://<netscaler-ip-address>/nitro/v1/config/cmpparameter

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 errorResponse Headers:

Content-Type:application/json

Response Payload:

{ "cmpparameter": [ {
"cmplevel":<String_value>,
"quantumsize":<Double_value>,
"servercmp":<String_value>,
"heurexpiry":<String_value>,
"heurexpirythres":<Double_value>,
"heurexpiryhistwt":<Double_value>,
"minressize":<Double_value>,
"cmpbypasspct":<Double_value>,
"cmponpush":<String_value>,
"policytype":<String_value>,
"addvaryheader":<String_value>,
"varyheadervalue":<String_value>,
"externalcache":<String_value>,
"builtin":<String[]_value>
}]}