Troubleshooting guide

1-10
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring Application Acceleration
Enabling and Disabling the Global Optimization Features
• HTTP 401 authentication required
Metadata caching is not applied in the following cases:
• Requests and responses that are not compliant with RFC standards
• URLs over 255 characters
• 301 and 401 responses with cookie headers
• HEAD method is used
• Pipelined transactions
Note The metadata caching feature is introduced in WAAS version 4.2.1, but version 4.2.1 is needed only on
the branch WAE. This feature can interoperate with an HTTP accelerator on a data center WAE that has
a lower version.
Using an HTTP Accelerator Subnet
The HTTP accelerator subnet feature allows you to selectively enable or disable specific HTTP
optimization features for specific IP subnets by using ACLs. This feature can be applied to the following
HTTP optimizations: HTTP metadata caching, HTTPS metadata caching, DRE hints, and suppress
server compression.
To define IP subnets, use the ip access-list global configuration command. Refer to this command in the
Cisco Wide Area Application Services Command Reference for information on configuring subnets. You
can use both standard and extended ACLs.
To configure a subnet for an HTTP accelerator feature, follow these steps:
Step 1 Enable the global configuration for all the HTTP accelerator features that you want to use.
Step 2 Create an IP access list to use for a subnet of traffic.
WAE(config)# ip access-list extended md_acl
WAE(config-ext-nacl)# permit ip 1.1.1.0 0.0.0.255 any
WAE(config-ext-nacl)# permit ip 2.2.2.0 0.0.0.255 3.3.3.0 0.0.0.255
WAE(config-ext-nacl)# exit
Step 3 Associate the ACL with a specific HTTP accelerator feature. Refer to the accelerator http global
configuration command in the Cisco Wide Area Application Services Command Reference for
information on associating an ACL with an HTTP accelerator feature.
WAE(config)# accelerator http metadatacache access-list md_acl
In this example, the HTTP metadata cache feature applies to all the connections that match the
conditions specified in the extended access-list md_acl.
In the following example, the HTTP suppress-server-encoding feature applies to all the connections that
match the conditions specified in the standard access-list 10.
WAE(config)# ip access-list standard 10
WAE(config-std-nacl)# permit 1.1.1.0 0.0.0.255
WAE(config-std-nacl)# exit
WAE(config)# accelerator http suppress-server-encoding accesslist 10