Cisco Cisco Web Security Appliance S160
Resolved Issues
40
Release Notes for Cisco IronPort AsyncOS 7.1 for Web
OL-23206-01
55163
Fixed: Application fault occurs when browsers send a malformed request to the
PAC server port on the Web Security appliance
PAC server port on the Web Security appliance
Previously, an application fault occurred when browsers sent a malformed request
containing NULL bytes to the PAC server port on the Web Security appliance. This
no longer occurs.
containing NULL bytes to the PAC server port on the Web Security appliance. This
no longer occurs.
55189
Fixed: Enabling the end-user acknowledgement page breaks the Policy Trace
feature
feature
Previously, enabling the end-user acknowledgement page broke the Policy Trace
feature. This no longer occurs.
feature. This no longer occurs.
55350
Fixed: Cannot join Active Directory domain after changing Web Security
appliance hostname in some cases
appliance hostname in some cases
Previously, joining the Active Directory domain did not work under the following
steps were applied:
steps were applied:
•
Configure the Web Security appliance hostname to a value that does not resolve
to the appliance itself.
to the appliance itself.
•
Create an NTLM authentication realm and try to join the Active Directory
domain. The Computer Account creation fails with the error message “Unknown
hostname.”
domain. The Computer Account creation fails with the error message “Unknown
hostname.”
•
Change the Web Security appliance hostname to a value that does resolve to itself,
and then try to join the domain again.
and then try to join the domain again.
AsyncOS for Web used the previous hostname to try and join the domain, so the
Computer Account creation failed again.
Computer Account creation failed again.
This no longer occurs.
55634
Fixed: Access policies show incorrect value for “HTTP/HTTPS Max Download
Size” setting in some cases
Size” setting in some cases
Previously, Access Policies showed the incorrect value for the “HTTP/HTTPS Max
Download Size” setting when it used the global policy values for the Object settings
and the Global Access policy was configured for a value other than the default value.
However, the Access Policies blocked transactions appropriately as configured in the
Global Access policy.
Download Size” setting when it used the global policy values for the Object settings
and the Global Access policy was configured for a value other than the default value.
However, the Access Policies blocked transactions appropriately as configured in the
Global Access policy.
This no longer occurs.
Table 4
Resolved Issues in AsyncOS 7.0 for Web (continued)
Defect ID
Description