Cisco Cisco Web Security Appliance S170 릴리즈 노트

When you use the 

updateconfig

 CLI command to change the update server, the new server 

does not appear in the web interface on the System Administration > Upgrade and Update 
Settings page.

Workaround: Ignore the value in the web interface, and instead use the CLI to view and edit 
the settings. [Defect ID: 67460] 

Attempting to import an AsyncOS 6.3.1 for Web Security configuration file to Configuration 
Master 6.3 results in error messages. 

Workaround: Prior to import, delete the following three lines from the configuration file:

<prox_config_http_port_tunneling_enabled>1

 

</prox_config_http_port_tunneling_enabled>

<prox_etc_allow_wild_card_in_group_name>1

 

</prox_etc_allow_wild_card_in_group_name>

<prox_etc_basic_auth_charset>ISO-8859-1</prox_etc_basic_auth_charset>

[Defect ID: 56116]

When deleting a route that does not exist on the Web Security appliance, the System Logs 
show the following warning message:

Warning: The following update to the interface failed: setfib -1 route -n delete route Reason: 
route: writing to routing socket: No such process

You can ignore this message. [Defect ID: 41304] 

The Web Security appliance sends the authenticated user name (X-Authenticated-User value) 
to external DLP servers in a format that is not compliant with the ICAP RFC. For some DLP 
vendors, such as Vontu, this may adversely affect reports or user name based policies. [Defect 
ID: 51433] 

The Web Security appliance sends HTTPS transactions to external DLP servers in a format that 
does not make it clear it is an HTTPS transaction instead of HTTP. Instead of sending HTTPS 
transactions as “https://uri” it sends them as the URI only. This may cause some DLP vendors,