Cisco Cisco Web Security Appliance S170
8
Release Notes for Cisco IronPort AsyncOS for Web 7.5.1-201
7.5.1
Resolved Issues
Resolved Issues in Version 7.5.1
Table 1
lists the issues that were resolved in version 7.5.1 of AsyncOS for Web.
Table 1
Resolved Issues in AsyncOS 7.5.1 for Web
Defect
ID
ID
Description
73467
Rebooting an appliance without a proper shutdown sometimes caused irreparable damage
to the appliance. This is fixed.
to the appliance. This is fixed.
73469
The Web Security appliance was sometimes sending out a non-applicable critical alert email
with the following message:
with the following message:
Counter group “MAIL_SYSTEM_CAPACITY” does not exist.
This is fixed.
77935
The Dynamic Content Analysis engine was erroneously overwriting the effective category
used in policy decisions for new requests. This is fixed.
used in policy decisions for new requests. This is fixed.
81055
Processing client requests sometimes took too long after updating new anti-malware rules.
This is fixed.
This is fixed.
81156
Attempting to navigate from Web Security Manager to the Outbound Malware Scanning
page was, in rare cases, producing an application fault. This is fixed.
page was, in rare cases, producing an application fault. This is fixed.
81408
The first web reputation database incremental update after upgrading AsyncOS for Web
failed in some cases depending on the Web Proxy load and time of day. This is fixed.
failed in some cases depending on the Web Proxy load and time of day. This is fixed.
81661
Overloading webroot made the WSA unusably slow. This is fixed.
82093
In deployments using WCCP, users were allowed to exceed the maximum number of entries
for Ports to Proxy without receiving an alert from the appliance. The maximum number of
port entries is 30 for HTTP, HTTPS, and FTP ports combined. Now, users can enter a
combination of port numbers and port ranges to reduce the number of entries, and AsyncOS
alerts users who exceed 30 entries. This defect is fixed.
for Ports to Proxy without receiving an alert from the appliance. The maximum number of
port entries is 30 for HTTP, HTTPS, and FTP ports combined. Now, users can enter a
combination of port numbers and port ranges to reduce the number of entries, and AsyncOS
alerts users who exceed 30 entries. This defect is fixed.
82415
Large Objects were taking too long to load in some cases when the client made a universal
range request. This is fixed.
range request. This is fixed.
82662
SNMP erroneously returned appliance information from the previous version of AsyncOS
after upgrading. This is fixed.
after upgrading. This is fixed.
82946
Non-UTF-8 characters in transaction header fields were resulting in unnecessary UTF-8
errors on the appliance. This is fixed.
errors on the appliance. This is fixed.
83479
When the disk reports a high temperature, AsyncOS sends out frequent, redundant alerts.
83666
With Safe Search enabled, for URLs that included a question mark (?) in the first position
after the domain name, for example, "example.com/?abc", transaction requests were
resulting in an HTTP 404 error message. This is fixed.
after the domain name, for example, "example.com/?abc", transaction requests were
resulting in an HTTP 404 error message. This is fixed.
84195
Transaction requests were sometimes resulting in HTTP 503 errors due to DNS caching
problems. This is fixed.
problems. This is fixed.
84293
Native FTP client transaction were sometimes hanging indefinitely when, while uploading
a file, the connection to the FTP server was reset, perhaps by a firewall. This is fixed.
a file, the connection to the FTP server was reset, perhaps by a firewall. This is fixed.
85730
Customers were experiencing poor performance and HTTP 504 errors when passing through
4000 or more HTTPS transaction requests. The problem was due to lingering HTTPS
connections tying up memory. This is fixed.
4000 or more HTTPS transaction requests. The problem was due to lingering HTTPS
connections tying up memory. This is fixed.