Cisco Cisco Web Security Appliance S670 User Guide

Access the CLI.

Use the 

advancedproxyconfig 

-> 

miscellaneous 

commands to access the required area 

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

[]> miscellaneous

Press Enter past each question until the question:

Do you want proxy to listen on P2?

 

Enter ‘y’ for this question.

Press Enter past the remaining questions.

Commit your changes.

.

.

Routes are used for determining where to send (or route) network traffic. The Web Security appliance 
routes the following kinds of traffic: 

Data traffic. Traffic the Web Proxy processes from end users browsing the web.

Management traffic. Traffic created by managing the appliance through the web interface and 
traffic the appliance creates for management services, such as AsyncOS upgrades, component 
updates, DNS, authentication, and more. 

By default, both types of traffic use the routes defined for all configured network interfaces. However, 
you can choose to split the routing, so that management traffic uses a management routing table and data 
traffic uses a data routing table. Both types of traffic split are split as follows: