Cisco Wide Area Virtualization Engine 274 Troubleshooting Guide Page 369

  • Download
  • Add to my manuals
  • Print
  • Page
    / 594
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 368
1-9
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring Application Acceleration
Enabling and Disabling the Global Optimization Features
Step 6 In the Minimum age of a cache entry field, enter the minimum number of seconds to retain HTTP header
information in the cache. The default is 60 seconds. Valid time periods range from 5 to 86400 seconds
(24 hours).
Step 7 Check the Enable local HTTP 301 redirect messages check box to enable the WAE to cache and locally
serve HTTP 301 messages. The default setting is checked.
Step 8 Check the Enable local HTTP 401 Authentication-required messages check box to enable the WAE
to cache and locally serve HTTP 401 messages. The default setting is checked.
Step 9 Check the Enable local HTTP 304 Not-Modified messages check box to enable the WAE to cache
HTTP 200 and 304 messages and locally serve HTTP 304 messages. The default setting is checked.
Step 10 To configure specific file extensions to which metadata caching is to be applied, enter the file extensions
in the File extension filters field at the far right. Separate multiple extensions with a comma (for
example: jpeg, gif, png) and do not include the dot at the beginning of the file extension. Click the
<< Add button to add the entered file extensions to the active list, which is shown to the left. You can
enter a maximum of 20 file extensions.
To remove an extension from the list, select it in the active list and click the >> Delete button.
By default, no file extension filters are defined and therefore metadata caching applies to all file types.
Step 11 Check the Suppress server compression for HTTP and HTTPS check box to configure the WAE to
suppress server compression between the client and the server. The default setting is checked.
By checking this box, you are telling the WAE to remove the Accept-Encoding value from HTTP and
HTTPS request headers, preventing the web server from compressing HTTP and HTTPS data that it
sends to the client. This allows the WAE to apply its own compression to the HTTP and HTTPS data,
typically resulting in much better compression than the web server for most files. For some file types
that rarely change, such as .css and .js files, this setting is ignored and web server compression is
allowed.
Step 12 Check the Enable DRE Hints for HTTP and HTTPS check box to send DRE hints to the DRE module
for improved DRE performance. The DRE hint feature is enabled by default.
Step 13 Click Submit.
The changes are saved to the device or device group.
To configure HTTP acceleration from the CLI, use the accelerator http global configuration command.
To show the contents of the metadata cache, use the show cache http-metadatacache EXEC command.
To clear the metadata cache, use the clear cache http-metadatacache EXEC command.
To enable or disable specific HTTP accelerator features for specific clients or IP subnets, use the HTTP
accelerator subnet feature. For more details, see the “Using an HTTP Accelerator Subnet” section on
page 1-10.
About HTTP Metadata Caching
The metadata caching feature allows the HTTP accelerator in the branch WAE to cache particular server
responses and respond locally to clients. The following server response messages are cached:
HTTP 200 OK (Applies to If-None-Match and If-Modified-Since requests)
HTTP 301 redirect
HTTP 304 not modified (Applies to If-None-Match and If-Modified-Since requests)
Page view 368
1 ... 368 369 370 ... 594

Comments to this Manuals

No comments