Comtech EF Data FX Series Administrator Guide - Manual (Page 125)

Comtech EF Data / Stampede
FX Series Administration Guide - Version 6.1.1 125
Chapter: FX Series Optimization Settings
Section: Configure Application Policies
MN-FXSERIESADM6 Rev 5
Application
The case-insensitive application name for this policy can be a partial name. For example, if “abc” is
specified, then this policy will apply to a URL containing “abc/def”. When the FX Series ADC matches a
URL against its application policies it will apply the most specific match that it encounters. If “abc/def” is
specified in addition to “abc”, then this policy will be used for a URL containing “abc/def/ghi”.
NOTE: Additionally, the application name of the policy can be “*” or empty. This is the default
application policy for this server. If no other match is found then this policy will be used. It is
possible to configure both a default server and a default application. This becomes the default policy that
is used when no server and application names match.
8.1.6 Authorization realm
This is a pull-down selector that enables you to limit the scope of this policy to a specific previously
defined authorization realm. Authorization realms (see Section 8.1.4 above) allow users to be grouped
based on source IP address or in-path interface.
Comment: Up to 80 characters of text can be entered to help document your configuration.
8.1.7 Enable Acceleration
Acceleration can be turned on or off.

When Enable Acceleration is “Yes”, the FX Series ADC will perform the acceleration techniques
that are enabled in this policy.

When Enable Acceleration is “No”, then, no acceleration techniques will be applied for
applications specified by this policy.

When a FX Series Remote or Plug-In is used and “Enable Acceleration is set to “No”, then the FX
Series Remote or Plug-In will pass the HTTP requests directly to the application server and bypass
the FX Series ADC. The default value is “No”.
8.1.8 Caching
Cache Data at ADC
This setting specifies if requested HTTP objects should be cached on the FX Series ADC. The “Guaranteed
object freshness time” also applies to these cached objects. The default is to cache the HTTP objects
(“Yes”).
Cache Data at Remote
This setting specifies if requested HTTP objects should be cached on the FX Series Remotes (REM). The
default is to cache the HTTP objects (“Yes”).
Enable Cache Differencing:
The FX Series ADC will cache dynamic content sent to a FX Series Remote or Plug-In enhanced browser.
On subsequent accesses to the same content, the FX Series ADC will send the changes rather than the
entire updated content and the FX Series Remote will edit the changes into its cache. The default is to
enable cache differencing (“Yes”).
8.1.9 Content Validation
Guaranteed Object Freshness Time (seconds)
This setting determines the number of seconds that will elapse after storing an object in the client
browser cache before the object must be verified for freshness. If the value is set to 0 then objects are
verified every time the object is accessed. The default value is 10800 seconds (3 hours).