Applies To:

Show Versions Show Versions

Manual Chapter: Variation Rules
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Accessing the Variation rule screen

If the WebAccelerator™ system receives two requests that are identical, except for the value of a query parameter defined in the variation rule, it creates a different UCI for each, and caches each response under its unique UCI, thus enabling different content to be served to respective UCIs.
  1. On the Main tab, click WebAccelerator > Policies. The Policies screen displays a list of existing acceleration policies.
  2. Click the name of a user-defined acceleration policy.
  3. Click a node in the Policy Tree.
  4. From the Matching Rules menu, choose Acceleration Rules.
  5. Click Variation.
The Variation page appears.

Variation rules matching

This table describes the Variation rules configuration settings and default values.

Variation rule Description
Host Matches a set of regular expressions against the Host header of the request. Typically you want to use Host matching to specify different content, for example, when differently named web sites deliver different content for the same URLs. A web site with identical content that is accessed through different host names, however, might require Host matching to Same Content.
Important: The Host header is required to determine which policy to apply, and must specify a value. An empty value or absent value matching is prohibited.
Query
Query Parameter
A specified value matches a named query parameter that appears in the URL or in the encoded body of a POST request. A named query parameter appears in the request as 'name=value', and is specified in the match value.
Unnamed Query Parameter
An unspecified value matches an unnamed query parameter that appears in the URL or in the encoded body of a POST request. An unnamed query parameter appears in the request as '=', and is unnamed because the parameter is unspecified. Because an unnamed query parameter is not explicitly designated, it is matched by means of its ordinal position, counted from left to right, in the query parameters of the request.
Note: You must assign an alias to an unnamed query parameter, which appears in the Name column of the parameter list, followed by the parenthetical ordinal.
All Query Parameters
Provides control of an unmatched, ambiguous query parameter that deviates from the name=value format.
Path Segment A specified value matches path segments in the request path as determined by the ordinal position, either left-to-right or right-to-left.
Note: You must assign an alias to a path segment parameter, which appears in the Name column of the parameter list, followed by the parenthetical ordinal.
Cookie A specified value matches cookie values included in Cookie and Cookie2 headers, for example, .
User Agent A specified value matches values in the User-Agent header, such as the name and version of the browser, and the operating system.
Referrer A specified value matches the values included in the Referer header, such as the URL of the page from which the user is coming.
Protocol A specified value matches the protocol used in the network connection, primarily intended to differentiate content served through an HTTP connection from content served through an HTTPS connection.
Header A specified value matches the value of a user-specified header.
Client IP A specified value matches the value of a client IP address in the network connection.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)