Cisco Cisco Web Security Appliance S170 Notas de publicación
13
Release Notes for Cisco IronPort AsyncOS 7.7.5 for Web
Related Documentation
Related Documentation
The documentation for the Cisco IronPort Web Security appliance includes the following:
•
Cisco Content Security Virtual Appliance Installation Guide
•
Cisco IronPort AsyncOS for Web User Guide
CSCzv46190
Attempting to delete a PAC file may result in misidentification of the file as the
default PAC file. This can happen if the name of the default PAC file includes special
characters.
default PAC file. This can happen if the name of the default PAC file includes special
characters.
Workaround: Don't use special characters in PAC file names.
CSCzv17778
AsyncOS and some browsers determine the root CA for each site using different
processes, which may result in discrepancies. Discrepancies may lead to unexpected
results when attempting to black list sites.
processes, which may result in discrepancies. Discrepancies may lead to unexpected
results when attempting to black list sites.
CSCzv50704
Web Security appliance performance is affected when the Default Proxy Logs are
configured at debug or trace logging level.
configured at debug or trace logging level.
Workaround: Change the logging level of the Default Proxy Logs to something higher
than Debug, such as Information.
than Debug, such as Information.
CSCzv36346
Running logconfig from the CLI and choosing 'Request Debug Logs' causes logging
and reporting to fail.
and reporting to fail.
CSCzv36740
Occasionally, network traffic moves faster than AsyncOS can accept the packets, and
the network adapter drops some packets.
the network adapter drops some packets.
CSCzv56650
Overriding the application type bandwidth limit for a particular application does 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.
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.
CSCzv69285
In deployments using WCCP, users who exceed the maximum number of entries
allowed for Ports to Proxy experience failures with IPFW rules and do not receive an
alert from the appliance. The maximum number of port entries is 30 for HTTP,
HTTPS, and FTP ports combined.
allowed for Ports to Proxy experience failures with IPFW rules and do not receive an
alert from the appliance. The maximum number of port entries is 30 for HTTP,
HTTPS, and FTP ports combined.
Workaround: Reduce the number of port entries to fewer than 30 for HTTP, HTTPS,
and FTP ports combined.
and FTP ports combined.
CSCzv60471
Certain browsers, including Firefox version 3 and Internet Explorer version 8, may
display their native error page instead of displaying the End-User Acknowledgement
or End-User Notification page configured through the appliance. Conditions:
display their native error page instead of displaying the End-User Acknowledgement
or End-User Notification page configured through the appliance. Conditions:
•
Protocol is HTTPS
•
Decryption is not enabled on the appliance.
Workaround: Enable decryption.
Bug Toolkit ID
Description