Applies To:

Show Versions Show Versions

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

12 
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. Responses cached rules, on the other hand, are based on specific HTTP response characteristics that the WebAccelerator system receives from the origin web server. These HTTP response parameters determine whether the WebAccelerator system should cache that content and under what conditions it should continue to cache that content, when the origin web server returns certain response codes.
By default, the WebAccelerator system only caches content that it considers complete. (For more information, see Caching responses.) One of the methods that the WebAccelerator system uses to determine if content is complete, is to verify that HTML pages contain both a begin and end HTML tag.
For troubleshooting purposes, you may require that the WebAccelerator system temporarily cache incomplete HTML content, until you determine why your application is not returning properly formed HTML pages. Using responses cached rules, you can configure the WebAccelerator system to override the default behavior and cache HTML content that does not contain a beginning and ending HTML tag.
NT LAN Manager, referred to as 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 received over an NTLM-authenticated connection, unless explicitly configured to do so.
By default, the WebAccelerator system only caches content from the origin web servers, if it contains the following HTTP response status codes:
You may have an application for which you want the WebAccelerator system to cache content returned with another status code. Using responses cached rules, you can configure the WebAccelerator system to override the default behavior and cache content received from the origin web server that contains the response codes defined in Table 12.1.
Table 12.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.
You organize responses cached on the Policy Tree, with any associated responses cached rules assigned to the leaf node. The Policy Tree is described in Chapter 4, Understanding the Policy Tree.
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 responses cached rule in its entirety at the parent node, when updating or modifying rules.
Caching Options
You specify the conditions in the response from the origin web server that prompt the WebAccelerator system to cache content
Responses Codes Cached
You specify which response codes returned from the origin web server prompts the WebAccelerator system to cache content
By default, the WebAccelerator system caches only responses that are complete. One of the methods that the WebAccelerator system uses to determine completeness is whether the response contains a matching begin and end HTML tag. 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 content that does 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 the existing 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.
By default, the WebAccelerator system does not cache content if it is requested over an NTLM connection. That is, the WebAccelerator system sends all requests that it receives over an NTLM connection, to the origin web server for content. However, you can override this behavior so that the WebAccelerator system does store NTLM-authenticated content.
Important: Override this default behavior only if you are certain that the per user, per object access rights used by NTLM authentication are unnecessary for your application 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 the existing 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.
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 on the Policy Tree as follows:
Home
This 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 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 responses 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 the existing 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.
4.
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.
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 from any screen within the Policy Editor to open the publish screen. We recommend that when you make a series of changes to an acceleration policy, you click the Publish button on the Policy Editor screen only after you make the last change in the series. Alternatively, you can publish an acceleration policy from the Policies screen. See Publishing acceleration policies, for more information.
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)