Cisco Cisco Web Security Appliance S380 Release Notes
Resolved Issues
36
Release Notes for Cisco IronPort AsyncOS 7.1.3 for Web
Resolved Issues in Version 7.0
lists the issues that were resolved in version 7.0 of AsyncOS for Web.
30070
Fixed: Reporting engine does not work and contains corrupt data after the
appliance shut down improperly
appliance shut down improperly
Previously, the reporting engine did not work and contained corrupt data after the
appliance shut down improperly. This no longer occurs.
appliance shut down improperly. This no longer occurs.
71985
Fixed: Application fault occurs when applying the Web Proxy feature key in the
web interface
web interface
Previously, an application fault occurred when applying the Web Proxy feature key in
the web interface. This no longer occurs.
the web interface. This no longer occurs.
72682
Fixed: Access log entries are not written when custom fields use incorrect syntax
Previously, when the access log subscription was configured to use format specifiers
with incorrect syntax, no entries were written to the access log file. This no longer
occurs. For a description of the correct syntax, see the “Logging” chapter in the Cisco
IronPort AsyncOS for Web User Guide.
with incorrect syntax, no entries were written to the access log file. This no longer
occurs. For a description of the correct syntax, see the “Logging” chapter in the Cisco
IronPort AsyncOS for Web User Guide.
Table 6
Resolved Issues in AsyncOS 7.1 for Web (continued)
Defect ID
Description
Table 7
Resolved Issues in AsyncOS 7.0 for Web
Defect ID
Description
71776
Fixed: Web Proxy runs out of memory and generates a core file when uploading
very large files in some cases
very large files in some cases
Previously, the Web Proxy ran out of memory and generated a core file when
uploading very large files to servers that sent an early HTTP 200 Ok response. This
no longer occurs.
uploading very large files to servers that sent an early HTTP 200 Ok response. This
no longer occurs.
71900
Fixed: Web Proxy processes requests very slowly due to a memory issue
Previously, the Web Proxy could get into a state where it processed requests very
slowly. This was due to a memory allocation issue. This no longer occurs.
slowly. This was due to a memory allocation issue. This no longer occurs.