Cisco Cisco Web Security Appliance S670 Guía Del Usuario
4-7
AsyncOS 9.1 for Cisco Web Security Appliances User Guide
Chapter 4 Intercepting Web Requests
Web Proxy Options for Intercepting Web Requests
Step 6
When you are finished entering values, press Enter until you are returned to the main command-line interface.
Step 7
Commit your changes.
Choosing The Web Proxy Cache Mode
Step 1
Access the CLI.
Step 2
Use the
advancedproxyconfig
->
caching
commands to access the required submenus:
example.com> advancedproxyconfig
Choose a parameter group:
- AUTHENTICATION - Authentication related parameters
- CACHING - Proxy Caching related parameters
- DNS - DNS related parameters
- EUN - EUN related parameters
- NATIVEFTP - Native FTP related parameters
- FTPOVERHTTP - FTP Over HTTP related parameters
- HTTPS - HTTPS related parameters
- SCANNING - Scanning related parameters
- PROXYCONN - Proxy connection header related parameters
- CUSTOMHEADERS - Manage custom request headers for specific domains
- MISCELLANEOUS - Miscellaneous proxy related parameters
- SOCKS - SOCKS Proxy parameters
[]> caching
Enter values for the caching options:
The following predefined choices exist for configuring advanced caching
options:
1. Safe Mode
2. Optimized Mode
3. Aggressive Mode
4. Customized Mode
Please select from one of the above choices:
[2]>
Step 3
Enter a number corresponding to the web proxy cache settings you require:
Entry
Mode
Description
1
Safe
The least caching and the most adherence to RFC #2616
compared to the other modes.
compared to the other modes.
2
Optimized Moderate
caching and moderate adherence to RFC #2616.
Compared to safe mode, in optimized mode the Web Proxy
caches objects when no caching time is specified when a
Last-Modified header is present. The Web Proxy caches
negative responses.
caches objects when no caching time is specified when a
Last-Modified header is present. The Web Proxy caches
negative responses.
3
Aggressive
The most caching and the least adherence to RFC #2616.
Compared to optimized mode, aggressive mode caches au-
thenticated content, ETag mismatches, and content without
a Last-Modified header. The Web Proxy ignores the
no-cache parameter.
Compared to optimized mode, aggressive mode caches au-
thenticated content, ETag mismatches, and content without
a Last-Modified header. The Web Proxy ignores the
no-cache parameter.
4
Customized mode
Configure each parameter individually.