Cisco Cisco Web Security Appliance S680 Release Notes

Page of 82
 
  Known Issues
56
Release Notes for Cisco IronPort AsyncOS 7.1.3 for Web
78517
Some FTP clients may time out and close the connection with the FTP Proxy 
early when uploading very large files and IronPort Data Security Policies are 
enabled 
Some FTP clients may time out and close the connection with the FTP Proxy early 
when uploading very large files and IronPort Data Security Policies are enabled. This 
results when the FTP Proxy requires more time to upload the file to the FTP server 
and the connection between the FTP client and the FTP Proxy has been idle for more 
than the configured time on the FTP client. Note that the FTP Proxy correctly uploads 
the file to the FTP server even if the FTP client closes its connection with the FTP 
Proxy.
Workaround: Increase the appropriate idle timeout value on the FTP client. 
78620
PAC file hosting erroneously appears disabled after loading a configuration file
When you enable PAC file hosting on the appliance, save the configuration, and then 
load the configuration, PAC file hosting is disabled on the Security Services > Proxy 
Auto-Configuration File Hosting page. Note, the appliance is correctly configured 
and serves PAC files to clients as necessary.
Workaround: Navigate to the Security Services > Proxy Auto-Configuration File 
Hosting page, and click Enable and Edit Settings. Verify the Enable Proxy 
Auto-Configuration File Hosting Settings option is checked, and submit your 
changes. You do not need to commit the changes to fix this problem in the web 
interface. 
70914
Policy Trace feature does not use the Dynamic Content Analysis engine when 
performing a trace 
The Policy Trace feature does not use the Dynamic Content Analysis engine when 
categorizing a URL when performing a trace. 
72238
Dynamic Content Analysis engine does not categorize web pages that contain 
NULL characters
The Dynamic Content Analysis engine does not categorize web pages that include 
characters containing NULL bytes. This might happen for web pages whose contents 
are UTF-16 encoded. 
Table 8
Known Issues for AsyncOS 7.1 for Web (continued)
Defect ID
Description