Activate F5 product registration key
Verify the proper operation of your BIG-IP system
Get up to speed with free self-paced courses
Join the community of 250,000+ technical peers
Advance your career with F5 Certification
Product Manuals and Release notes
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, however, 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 system’s default behavior by modifying the following options for responses cached rules.
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 might 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 responses cached rules to 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 response codes to prompt the WebAccelerator system to cache content.
This topic 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.
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.