Cisco Cisco Web Security Appliance S380
33
Release Notes for Cisco IronPort AsyncOS 7.5.0-838 for Web
Known Issues
71912
Google Talk clients cannot successfully log into Google Talk when the HTTPS Proxy
decrypts traffic in some cases. Google Talk clients cannot successfully log into
Google Talk under the following conditions:
decrypts traffic in some cases. Google Talk clients cannot successfully log into
Google Talk under the following conditions:
•
The Web Proxy is deployed in explicit forward mode.
•
The HTTPS Proxy decrypts the Google Talk traffic.
•
The Access Policy applied to the Google Talk transaction is not configured to use
port 5222 as an HTTP CONNECT Port.
port 5222 as an HTTP CONNECT Port.
Workaround: Edit the Access Policy that applies to Google Talk transactions and add
port 5222 as an HTTP CONNECT Port.
port 5222 as an HTTP CONNECT Port.
73469
Appliance sends out a non-applicable critical alert email in some cases
The Web Security appliance sometimes sends out a non-applicable critical alert email
with the following message:
with the following message:
Counter group “MAIL_SYSTEM_CAPACITY” does not exist.
76210
Traceback generated after technical support tunnel fails for reasons related to
DNS.
DNS.
When attempting to establish a secure tunnel through which Cisco IronPort technical
support can connect to the Appliance, if the tunnel attempt fails for reasons related to
DNS, AsyncOS generates a traceback.
support can connect to the Appliance, if the tunnel attempt fails for reasons related to
DNS, AsyncOS generates a traceback.
79535
System Capacity reports and logs show CPU activity for some features that are
disabled
disabled
System Capacity reports and logs may show CPU activity for Web Reputation and
Web Categorization when those features are disabled. This is because these measures
also include activity related to other services.
Web Categorization when those features are disabled. This is because these measures
also include activity related to other services.
81408
First web reputation database incremental update after upgrading AsyncOS for
Web fails in some cases
Web fails in some cases
The first web reputation database incremental update after upgrading AsyncOS for
Web fails depending on the Web Proxy load and time of day.
Web fails depending on the Web Proxy load and time of day.
Workaround: Wait until the next full web reputation database update which will occur
in less than 24 hours.
in less than 24 hours.
82852
Overriding the application type bandwidth limit for a particular application does
not work
not work
When you define a bandwidth limit for an application type and then override that limit
by choosing no bandwidth for a particular application in that application type, the
Web Proxy erroneously still applies the defined bandwidth limits to the application.
by choosing no bandwidth for a particular application in that application type, the
Web Proxy erroneously still applies the defined bandwidth limits to the application.
Table 4
Known Issues for AsyncOS 7.5.0 for Web (continued)
Defect ID
Description