Applies To:

Show Versions Show Versions

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

The WebAccelerator® system uses matching rules to classify a request or response and generate an object type. For requests, the classification is based on the file extension present in the request. For example, a matching rule might specify that the WebAccelerator system place all requests with a .gif extension into a group for images.
Once the WebAccelerator system classifies a request or response by object type, it performs application matching which consists of:
For an HTTP request or response to match to a specific leaf node, it must match all the matching rules defined for the leaf node. Once you create the matching rules for an acceleration policy, you can configure the various acceleration rules to handle requests. For example, for images files you might have a matching rule based on common image extensions found in HTTP requests. In this case, an Image leaf node on the Policy Tree with a matching rule for requests that contain an extension of gif, GIF, jpg, JPG, jpeg, or JPEG. When the WebAccelerator system matches a request to the Image node, it applies the associated acceleration rules to manage image files for your site.
1.
In the navigation pane, expand WebAccelerator and click Policies.
The Policies screen displays a list of existing acceleration policies.
4.
From the Add Parameter list, select a parameter, and then click the Add button.
6.
Click the Save button.
For a new or modified acceleration policy to be in effect for your site, you must publish it. One way to do this is to click the Publish button.
Leaf node 1
Contains matching rules based on three query parameters.
Leaf node 2
Contains matching rules based on two of the same three query parameters as Leaf node 1.
A request that matches all three query parameters is considered a match. However, the WebAccelerator system matches the request to Leaf node 1, because that node is a superset and is the best match.
Leaf node 1
Contains three matching rules based on three query parameters.
Leaf node 2
Contains two matching rules based on two query parameters.
Then query is considered ambiguous, because the matching rules do not dictate that one leaf node is a better match than another node. For ambiguous queries, the WebAccelerator system chooses between the leaf nodes based on their priority on the Policy Tree.
In addition to precedence, the WebAccelerator system attempts to match first to the following two HTTP request data type parameters, when performing application matching:
Matching rules based on the path parameter have first priority over all other parameter matches and the WebAccelerator system always chooses an exact path match before other path matches. An exact path match is one where the value set for the path parameter includes the question mark. For example, if you have a rule with the following path parameter value:
the WebAccelerator system considers the following request an exact match, and matches the request to the leaf node to which the rule belongs.
It is important to note that a path of / and /? are two different things. A path that includes a ? indicates that an exact match is required.
By default, a path that you provide for a policy is a prefix. For example, if you give a parameter the path, /a/b, the WebAccelerator system considers both of the following requests a match:
If you add a question mark to the parameter so that it is, /a/b?, the WebAccelerator system considers only the following a match, because the question mark indicates that an exact match is required.
Matching rules based on the extension parameter have the second priority over other parameter matches. If the extension on a request matches the extension parameter specified by a matching rule, the WebAccelerator system matches the request to the leaf node to which the rule belongs.
If a request does not match a leaf node on the Policy Tree, the WebAccelerator system either uses a predefined accelerator policy that manages unmatched requests and responses, or sends the request to the origin web server for content.
It is important to keep in mind that for the WebAccelerator system to consider a request a match, the request must match all the matching rules configured for a leaf node. If a request matches all the rules for a leaf node, except for one, the WebAccelerator system does not consider it a match, and processes it as an unmapped request.
This section of the chapter provides information about how to configure an example matching rule. For this example site, you have three top-level nodes on the Policy Tree as follows:
Home
This branch node specifies the rules related to the home page.
Applications
This branch node specifies the rules related to the applications for the site, with the following leaf nodes:
Default
This leaf node specifies the rules related to non-search related applications.
Search
This leaf node specifies the rules related to your sites search application.
Images
This branch node specifies the rules related to graphics images.
1.
In the navigation pane, expand WebAccelerator and click Policies.
The Policies screen displays a list of existing acceleration policies.
4.
From the Add Parameter list, select Path, and click the Add button.
5.
In the Value(s) box, type the values for each node, as specified in Table 5.1.
6.
Click the Save button.
For a new or modified acceleration policy to be in effect for your site, you must publish it. One way to do this is to click the Publish button.
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)