Cisco Cisco Web Security Appliance S380

ページ / 54
 
30
Release Notes for Cisco IronPort AsyncOS 7.5.0-838 for Web
  Resolved Issues
76185
Fixed: Files greater than the maximum allowed file size are erroneously 
uploaded using FTP in some cases
 
Previously, files greater than the maximum allowed file size were erroneously 
uploaded when an IronPort Data Security policy was configured to block FTP 
transactions greater than a specified size. The access logs showed that the file was 
blocked, but in reality the file was successfully transferred to the FTP server. This no 
longer occurs. 
73339
Fixed: Log file timestamps and log file headers show incorrect time after 
changing the time zone in some cases
 
Previously, when you changed the time zone on the appliance, the time zone change 
was not propagated to the internal logging process. As a result, the timestamps in the 
log filename and the offset in the log file headers were incorrect. (However, the log 
entries in the log files correctly used the new time zone.) This no longer occurs. 
72834
Fixed: An application fault occurs in the internal reporting process when you 
change the system time or time zone on the appliance in some cases
Previously, an application fault occurred in the internal reporting process when you 
changed the system time or time zone on the appliance after it had processed traffic. 
Additionally, for some appliances, data was not aggregated properly (for example, 
hourly data was not aggregated into the daily data). This no longer occurs. 
72835
Fixed: Export link is missing on the Reports By User Location report page for 
the “Suspect Transactions Detected” charts
Previously, the Export link was missing on the Reports By User Location report page 
for the “Suspect Transactions Detected” charts for both Remote and Local users. This 
no longer occurs.
72432
Fixed: PDF file of Web Tracking report does not include related transactions 
information
Previously, when you displayed the related transactions in a Web Tracking report and 
then printed to PDF, the PDF file did not contain the related transactions information. 
This no longer occurs. 
70537
Fixed: Web Proxy erroneously does not recognize some root authorities
Previously, by default, the Web Proxy erroneously did not recognize the “VeriSign 
Class 3 Secure Server CA” root certificate. The Web Proxy did not recognize the root 
authority of websites that use this root certificate to establish its trust relationship. 
Depending on how the HTTPS Proxy was configured to handle invalid certificates, 
client requests to these sites may have been dropped. This no longer occurs. 
Table 3
Resolved Issues in AsyncOS 7.5.0 for Web (continued)
Defect ID
Description