
4
Release Note for Cisco ACNS Software, Release 5.5.7
OL-13139-01
HTTP Follow-Redirect Feature
After initial setup, which requires using router configuration commands, configure the NME-WAE in the
same manner as other ACNS devices, with the following exceptions:
• The NME-WAE cannot serve as a Content Distribution Manager for other ACNS devices.
• The NME-WAE does not support devicemode configuration. The devicemodeconfiguration prompt
has been removed from the NME-WAE startup script.
• Websense URL-filtering is not supported for the NME-WAE-502.
The ACNS software does not support the following hardware-related features for the network module:
• USB port
• Compact Flash utilization LED
• Software reset button
Note Although the software does not support the software reset button, the hardware will reset if you press
the reset button for more than 4 seconds.
HTTP Follow-Redirect Feature
The ACNS 5.5.7 software supports a new HTTP and HTTPS filtering option (http follow-redirect) that
allows the Content Engine to access content objects from a list of servers that match the hostname (or
IP address) and URL path prefix that you specify in the configuration. This feature allows ACNS to host
content and provide accelerated delivery for third-party applications that use dynamically-generated
access URLs.
This section describes the HTTP follow-redirect feature and contains the following configuration
information:
• Configuring HTTP Follow-Redirect Filtering Using the Content Distribution Manager GUI
• Configuring HTTP Follow-Redirect Filtering Using the Content Engine CLI
• Viewing HTTP Follow-Redirect Filtering Statistics
• Configuring a Custom Error Page
To implement this feature, three new global configuration commands have been added to the CLI and
corresponding configuration settings have been added to the Content Distribution Manager GUI. You
must enter all three of these new commands to configure the Content Engine to intercept and follow the
HTTP or HTTPS 302 redirect responses.
If you enable this feature, but do not configure all of these commands, then the 302 response from the
issuing server is sent directly to the client instead of to the Content Engine, and the location of the origin
server is exposed to the client. The result occurs when the CLI-configured hostname does not match the
hostname in the request from client or when the CLI-configured path prefix does not match the prefix in
the 302 redirect URL received by the Content Engine.
If you do not configure the username and password, or if the username or password is rejected by the
origin server, the server sends a standard 500 class error code to the client. In ACNS 5.5.7 software, you
may configure the Content Engine to download and send a customized error message page instead of the
standard error message.
Comentarios a estos manuales