Applies To:

Show Versions Show Versions

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

13 
Most acceleration rules are based on information that is contained in a request. For example, when a particular query parameter is set to a certain value, it prompts the WebAccelerator system to perform a specified function, or the WebAccelerator system provides a specific response based on the presence or absence of a cookie in a request. Response cached rules, on the other hand, are based on information that is contained in the response, and provide the WebAccelerator system with the information it needs to determine if it should cache the content it receives from the origin web server.
When using a response cached rule, the WebAccelerator system evaluates the response that matches to the node, for which the response cached rule is defined, to determine whether it should cache the response.
You organize responses cached in the Policy Tree, with any associated responses cached rules assigned to the leaf node. The Policy Tree is described in Chapter 4, Introducing the Policy Tree.
Each leaf node in the Policy Tree can have up to one responses cached rules defined for it. Responses cached rules are inherited from a parent node in their entirety. Unlike other types of acceleration rules where you can add to an inherited rule, you must override a response cached rule in its entirety at the parent node, when updating or modifying rules.
The WebAccelerator system only caches content in a response if it considers the content complete. The WebAccelerator system uses different methods to determine if content is complete, based on the type of data contained within the response as follows:
HTML tags
If the response is an HTML page, the WebAccelerator system considers content complete only if it contains both beginning and ending HTML tags. If you override this default requirement, the WebAccelerator system uses information in the HTTP response headers to determine if the response is complete.
HTTP response headers
If the response is anything other than an HTML page, or if you have overridden the requirement described in the previous bullet point, the WebAccelerator system considers content complete only if the response body size matches the value specified on the Content-Length response header.
Chunked transfer coding
If you do not use the Content-Length header for the response, you must use chunked transfer coding. If you use chunked transfer coding, theWebAccelerator system does not consider content complete until it receives the final zero-sized chunk. For information about chunked transfer coding, see section 3.6 in the HTTP/1.1 specification http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6
If you do not want the WebAccelerator system to require matching begin and end HTML tags in order to consider content complete, you can override this default behavior using the following procedure.
To allow the WebAccelerator system to cache documents that do not contain matching begin and end HTML tags
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen opens in a new window.
2.
On the Main tab of the navigation pane in the new window, click Policies.
The Policies screen opens, displaying a table of user-defined and pre-defined acceleration policies.
3.
On the User-defined Acceleration Policies table, click the name of the acceleration policy that you want to edit.
The Policy Editor screen opens.
5.
From the Matching Rules list on the Policy Editor menu bar, select Acceleration Rules.
The acceleration rules display on the Policy Editor menu bar.
6.
On the Policy Editor menu bar, click Responses Cached.
The Responses Cached Rules screen opens.
7.
In the Caching Options area, clear the check box for Cache only if the document contains matching begin and end tags.
8.
Click the Save button.
NT LAN Manager (NTLM) is a suite of authentication and session security protocols used in various Microsoft® network protocol implementations and is widely used by the Microsoft® Windows NT® family of products to safeguard sensitive information.
By default, the WebAccelerator system does not cache content if it was requested over an NTLM connection. However, you can override this behavior so that the WebAccelerator system stores NTLM-authenticated content
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen opens in a new window.
2.
On the Main tab of the navigation pane in the new window, click Policies.
The Policies screen opens, displaying a table of user-defined and pre-defined acceleration policies.
3.
On the User-defined Acceleration Policies table, click the name of the acceleration policy that you want to edit.
The Policy Editor screen opens.
5.
From the Matching Rules list on the Policy Editor menu bar, select Acceleration Rules.
The acceleration rules display on the Policy Editor menu bar.
6.
On the Policy Editor menu bar, click Responses Cached.
The Responses Cached Rules screen opens.
7.
In the Caching Options area, check the box for Cache content received over NTLM-authenticated connection.
8.
Click the Save button.
10.
Edit the pvsystem.conf file.
11.
Locate the <accelerateNTLM>false</accelerateNTLM> line and change it to true.
12.
Locate the <enableAutoNTLMAuth>false</enableAutoNTLMAuth> line and change it to true.
13.
Save and exit the pvsystem.conf file.
By default, the WebAccelerator system only caches content from the origin web servers, if it contains the following HTTP response codes:
You can use responses cached rules to instruct the WebAccelerator system to cache responses for content that contains the response codes defined in Table 13.1.
Table 13.1 Response codes
Multiple Choices
The requested resource has multiple possibilities, each with different locations.
Moved Permanently
The requested content has been permanently assigned a new URI. The origin web server is responding with a redirect to the new location for the content.
Found
The requested content temporarily resides under a different URI. The redirect to the new location may change.
Temporary Redirect
The requested content temporarily resides under a different URI. The redirect to the new location may change.
Gone
The requested content is no longer available and a redirect is not available.
This section of the chapter provides information about how to configure an example responses cached rule. For this example site, you have three top-level nodes in 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.
Note: See To create the Home, Application, and Images nodes for the example Policy Tree, for specific instructions about how to create the Policy Tree.
For this example, your site had an application requested as http://www.siterequest.com/apps/magic.jsp, but due to current development on your site, it is temporarily requested as http://www.siterequest.com/apps/magicact.jsp.
As a result of this change, the WebAccelerator system handles requests for the http://www.siterequest.com/apps/magic.jsp with a temporary redirect to http://www.siterequest.com/apps/magicact.jsp.
For this example, add a response cached rule to the default node (which is inherited by all leaf nodes) that indicates that the WebAccelerator system should cache content that contains a 307 response code.
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen opens in a new window.
2.
On the Main tab of the navigation pane in the new window, click Policies.
The Policies screen opens, displaying a table of user-defined and pre-defined acceleration policies.
3.
On the User-defined Acceleration Policies table, click the name of the acceleration policy that you want to edit.
The Policy Editor screen opens.
5.
From the Matching Rules list on the Policy Editor menu bar, select Acceleration Rules.
The acceleration rules display on the Policy Editor menu bar.
6.
On the Policy Editor menu bar, click Responses Cached.
The Responses Cached Rules screen opens.
7.
In the Response Codes Cached area, check the 307 - Temporary Redirect check box.
8.
Click the Save button.

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)