Cisco Cisco Web Security Appliance S170 Notas de publicación
I R O N P O R T A S Y N C O S 6 . 3 . 7 F O R W E B R E L E A S E N O T E S
31
Fixed: McAfee scanning engine stops working after a feature key is updated in some
cases resulting in latency
cases resulting in latency
Previously, the McAfee scanning engine stopped scanning transactions when the McAfee
feature key expired and then was updated. This resulted in slow response times for
transactions. This no longer occurs. Now, McAfee scanning works after the feature key is
updated after expiration and no latency is observed. [Defect ID: 50591]
feature key expired and then was updated. This resulted in slow response times for
transactions. This no longer occurs. Now, McAfee scanning works after the feature key is
updated after expiration and no latency is observed. [Defect ID: 50591]
Fixed: Web Proxy stops processing transactions after upgrading from a version with an
invalid configuration in some cases
invalid configuration in some cases
Previously, the Web Proxy stopped processing transactions and the proxy logs showed error
messages saying, “Couldn’t determine available system storage.” This happened after
upgrading from a previous version that had a custom URL category that was deleted, but the
configuration file still had some residual references to the deleted custom URL category. This
no longer occurs. [Defect ID: 50839]
messages saying, “Couldn’t determine available system storage.” This happened after
upgrading from a previous version that had a custom URL category that was deleted, but the
configuration file still had some residual references to the deleted custom URL category. This
no longer occurs. [Defect ID: 50839]
Fixed: Web Proxy does not start when it fails nslookups on its own IP address
Previously, the Web Proxy did not start when it failed nslookups on its own IP address. This no
longer occurs. [Defect ID: 50853]
longer occurs. [Defect ID: 50853]
Fixed: Web Proxy generates a core file when processing very long URIs in some cases
Previously, the Web Proxy generated a core file when processing very long URIs after an
internal failure. This no longer occurs. [Defect ID: 50986]
internal failure. This no longer occurs. [Defect ID: 50986]
Fixed: Wrong action taken on upload requests with IronPort Data Security Policies and
custom URL categories in some cases
custom URL categories in some cases
Previously, when an upload request was matched to an IronPort Data Security Policy, and the
URL in the request matched a custom URL category set to Monitor, the Web Proxy applied the
action defined for the applicable predefined URL category instead. This no longer occurs.
[Defect ID: 51027]
URL in the request matched a custom URL category set to Monitor, the Web Proxy applied the
action defined for the applicable predefined URL category instead. This no longer occurs.
[Defect ID: 51027]
Fixed: HTTP requests fail when the request header is slightly smaller than 16K in size
Previously, HTTP requests failed when the request header was slightly smaller than 16K in
size. This no longer occurs. [Defect ID: 51083]
size. This no longer occurs. [Defect ID: 51083]
Fixed: CPU utilization rate is very high with a large number of policies
Previously, the CPU utilization rate was very high with a large number of policies. This no
longer occurs. [Defect ID: 51362]
longer occurs. [Defect ID: 51362]
Fixed: Application fault occurs in the CLI when creating a new Request Debug log
Previously, an application fault occurred in the CLI when creating a new Request Debug log
using the
using the
logconfig
CLI command. This no longer occurs. [Defect ID: 51406]