Cisco Cisco Web Security Appliance S670

36

C I S C O   I R O N P O R T   A S Y N C O S   6 . 3 . 8   F O R   W E B   R E L E A S E   N O T E S

Previously, the Web Proxy generated a core file when a client application used HTTP 
pipelining (multiple HTTP requests are written out to a single socket without waiting for the 
corresponding responses) due to internal memory management issues. This no longer occurs. 
[Defect ID: 50248] 

Previously, the Web Proxy generated a core file and restarted multiple times a day when 
fetching content from the memory cache. This no longer occurs. [Defect ID: 50405] 

Previously, users experienced slow response times after the McAfee license expired on the 
Web Security appliance. This no longer occurs. [Defect ID: 50449] 

Previously, the Web Proxy generated a core file when processing malformed HTTP requests 
that tried to connect to the non-existent port 0 on the server. This no longer occurs. [Defect 
ID: 51084] 

Previously, an application fault occurred when trying to specify subnets for Access Policy 
membership when no Identity was selected. This no longer occurs. [Defect ID: 51123] 

Previously, DNS lookups failed when using the routing table on the Data network interface. 
This no longer occurs. [Defect ID: 51139, 51140] 

Previously, administrators could not change the state (to enabled or disabled) of the End-User 
Misclassification Reporting field on the Security Services > End-User Notification page. The 
GUI made it appear as if the change took effect, but the Web Security appliance configuration 
did not change. This no longer occurs. [Defect ID: 48886] 

Previously, an application fault occurred in an internal process and an alert was sent after the 
following steps were taken:

• The global Access Policy was configured to take action on a predefined URL category 

based on a time range.

• The time range used by the global Access Policy was deleted.