Cisco Cisco Web Security Appliance S680 Guía Del Usuario
Chapter 5 Web Proxy Services
Advanced Proxy Configuration
5-30
Cisco IronPort AsyncOS 7.0 for Web User Guide
OL-23079-01
Note
These steps also work with Internet Explorer. However, for Internet Explorer
version 6, create a copy of wpad.dat and name it wpad.da.
version 6, create a copy of wpad.dat and name it wpad.da.
Advanced Proxy Configuration
AsyncOS includes the
advancedproxyconfig
CLI command so you can configure
more advanced Web Proxy configurations, such as authentication and DNS
parameters.
parameters.
The
advancedproxyconfig
command includes the following subcommands:
•
Authentication. Configure authentication parameters, such as the number of
outstanding concurrent Basic or NTLMSSP authentication requests to be
authenticated by the authentication server and whether or not to log the
username that appears in the request URI. You can also use the
outstanding concurrent Basic or NTLMSSP authentication requests to be
authenticated by the authentication server and whether or not to log the
username that appears in the request URI. You can also use the
authentication
subcommand to enable the user acknowledgment page. For
more information about the user acknowledgment page, see
.
For more information, see
.
•
Caching. Configure advanced Web Proxy caching options, such as:
–
Whether or not to ignore client requests to not retrieve content from the
proxy cache
proxy cache
–
Whether or not to cache content from an untrusted server
You can configure the parameters separately by selecting “Customized
Mode,” or you can choose a predefined set of parameter values. You can
choose the following modes:
Mode,” or you can choose a predefined set of parameter values. You can
choose the following modes:
–
Safe mode. This mode uses less caching.
–
Optimized mode. This mode uses moderate caching.
–
Aggressive mode. This mode uses aggressive caching.
For more information, see
•
DNS. Configure DNS-related options, such as the time to cache results of
DNS errors and whether or not the Web Proxy should issue an HTTP 302
redirection on DNS lookup failure.
DNS errors and whether or not the Web Proxy should issue an HTTP 302
redirection on DNS lookup failure.