Cisco Cisco Web Security Appliance S170 릴리즈 노트

40

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

B U G S   F I X E D   I N   6 . 0 . 0

Previously, some web pages took several minutes to load when a web page component 
returned a 5xx response due to the Web Proxy sending the body content twice. This no longer 
occurs. Now, web pages load normally and the Web Proxy sends the body content once. 
[Defect ID: 52020]

Previously, the Web Proxy generated a core file when a transaction uploaded data using a 
persistent connection and the data was scanned by the IronPort Data Security Filters. This 
happened quite often with Adobe Flash applications. This no longer occurs. [Defect ID: 
51813]

Previously, alerts failed to get sent when the Web Security appliance was configured to use 
separate networks for Management and Data traffic and the SMTP server used for sending the 
alerts was not accessible from the Data network interface. This no longer occurs. [Defect ID: 
51693] 

Previously, HTTP requests failed when the request header was slightly smaller than 16K in 
size. This no longer occurs. [Defect ID: 51083] 

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, the Web Proxy generated a core file when trying to satisfy a range request with an 
invalid range for a large object served from cache. This no longer occurs. [Defect ID: 43813] 

Previously, the Web Proxy generated a core file when an idle native FTP client issued a QUIT 
command. This no longer occurs. [Defect ID: 49469]