Cisco Cisco Web Security Appliance S170
I R O N P O R T A S Y N C O S 6 . 3 . 7 F O R W E B R E L E A S E N O T E S
39
B U G S F I X E D I N 6 . 0 . 0
Fixed: Some web pages take several minutes to load when a web page component
returns a 5xx response
returns a 5xx response
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]
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]
Fixed: Web Proxy generates a core file when uploading data with persistent connections
and IronPort Data Security Filters enabled in some cases
and IronPort Data Security Filters enabled in some cases
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]
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]
Fixed: Alerts fail to get sent when the Web Security appliance is configured to use
separate networks for Management and Data traffic in some cases
separate networks for Management and Data traffic in some cases
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]
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]
Fixed: Web Proxy generates a core file when a client application uses HTTP pipelining
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]
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]
Fixed: HTTP requests fail when the request header is slightly smaller than 16K in size
Previously, HTTP requests failed when the request header was slightly smaller than 16K in
size. This no longer occurs. [Defect ID: 51083]
size. This no longer occurs. [Defect ID: 51083]
Fixed: Web Proxy generates a core file when processing some malformed HTTP requests
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]
that tried to connect to the non-existent port 0 on the server. This no longer occurs. [Defect
ID: 51084]
Fixed: Web Proxy generates a core file serving a very large cached response in some
cases
cases
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]
invalid range for a large object served from cache. This no longer occurs. [Defect ID: 43813]