Академический Документы
Профессиональный Документы
Культура Документы
Contents
HTTP Compression............................................................................................
11
HTTP Compression
The NetScaler ADC can apply GZIP or DEFLATE algorithms to compress the HTTP responses
sent from your servers to client browsers that support compression. Compressed responses
use less bandwidth and improve website performance. The compressed responses can
include both static and dynamically generated data.
Compression is a policy based feature that supports both classic and advanced policies. You
enable the feature globally or at the service level, and bind a compression policy globally or
to a virtual server. The policy specifies the type of traffic to compress.
To configure compression, you must have a basic understanding of NetScaler policies. For
more information about policies, see "Policies and Expressions."
At global level
enable ns feature cmp
At service level
set service <name> -CMP YES
Note: Compression can be enabled only for HTTP and SSL services.
2. [Optional] Configure compression parameters that apply globally.
set cmp parameter -cmpLevel <cmpLevel> -quantumSize <integer> [-addVaryHeader (
ENABLED | DISABLED ) [-varyHeaderValue <string>]]...
Note: Vary header parameters are available from NetScaler 10.5 onwards.
3. Create a compression action to specify the type of compression to be performed on the
HTTP response.
At global level
bind cmp global <policyName> [-priority <positive_integer>] [-state
(ENABLED|DISABLED)]...
At virtual server
At global level
Navigate to System > Settings, click Configure Basic Features, and select HTTP
Compression.
At service level
Navigate to Traffic Management > Load Balancing > Services, select the service and
in the Settings group, enable Compression.
2. [Optional] Configure compression parameters that apply globally.
Navigate to Optimization > HTTP Compression, click Change Compression Settings and
set the relevant parameters.
3. Create a compression action to specify the type of compression to be performed on the
HTTP response.
Navigate to Optimization > HTTP Compression > Actions, click Add, and create a
compression action.
4. Create a compression policy to specify the condition on which the action will be
performed.
Navigate to Optimization > HTTP Compression > Policies, click Add and create a
compression policy by specifying the condition and the corresponding action to be
executed.
5. Bind a compression policy to specify the point at which the policy will be evaluated.
At global level
Navigate to Optimization > HTTP Compression > Policies, click Policy Manager and
bind the required policies by specifying the relevant Bind Point and Connection
Type (Request/Response).
At virtual server level
For load balancing. Navigate to Traffic Management > Load Balancing > Virtual
Servers, select the required virtual server and click Policies to bind the relevant
policy.
For content switching. Navigate to Traffic Management > Content Switching >
Virtual Servers, select the required virtual server and click Policies to bind the
relevant policy.
To view run-time statistics, navigate to Optimization > HTTP Compression, click Statistics.
set service
name
Name of the service for which to modify parameters.
CMP
Enable compression for the service.
Possible values: YES, NO
View description(s) in command reference Top
bind lb vserver
policyName
Name of the policy to bind to the virtual server.
View description(s) in command reference Top
stat cmp
No parameters provided in this topic or the command has no parameters. View
description(s) in command reference Top
10
11
Policy
Type
Description
ns_cmp_content_type
Classic
ns_adv_cmp_content_t
ype
Advanc
ed
ns_cmp_msapp
Classic
ns_adv_cmp_msapp
Advanc
ed
ns_cmp_mscss
Classic
ns_adv_cmp_mscss
Advanc
ed
ns_nocmp_mozilla_47
Classic
ns_adv_nocmp_mozilla
_47
Advanc
ed
ns_nocmp_xml_ie
Classic
ns_adv_nocmp_xml_ie
Advanc
ed