Applies To:

Show Versions Show Versions

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

11 
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 WebAcceleratorTM 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.
You can override the WebAccelerator systems default behavior by modifying the following options for responses cached rules.
Caching HTML Documents
Specifies whether an HTML response from the origin web server must contain matching begin and end HTML tags for WebAccelerator system to cache the content. By default, the WebAccelerator system caches only responses that are complete.
Responses Codes Cached
Specifies which response codes returned from the origin web server prompt the WebAccelerator system to cache content. By default, the WebAccelerator system caches content when the origin web server returns 200, 201, 203, or 207 response codes. You cannot change this default behavior, but you can specify additional codes.
1.
In the navigation pane, expand WebAccelerator and click Policies.
4.
From the Matching Rules list on the Policy Editor menu bar, select Acceleration Rules.
5.
Click Responses Cached.
7.
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.
By default, the WebAccelerator system caches content only if it is complete. One way the WebAccelerator system determines if content is complete, is to verify that HTML pages contain both a begin and end HTML tag.
However, 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. To do this, you can configure a responses cached rules override this default behavior and cache HTML content that does not contain both a begin and end HTML tag.
The WebAccelerator system always caches content from the origin web servers if it contains an HTTP 200, 201, 203, or 207 response status code. You cannot change this default behavior. However, you can specify additional responses codes to prompt the WebAccelerator system to cache content. Those response codes are defined in Table 11.1.
Table 11.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 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.
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.
To manage this change, 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.
In the navigation pane, expand WebAccelerator and click Policies.
3.
4.
From the Matching Rules list on the Policy Editor menu bar, select Acceleration Rules.
5.
Click Responses Cached.
6.
In the Response Codes Cached area, check the 307 - Temporary Redirect check box.
7.
Click Save.
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)