Cisco Cisco Web Security Appliance S670 Release Notes

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

Fixed: Uploads fail and the Web Proxy generates a core with upstream proxy servers in
some cases

Previously, uploads to web servers going through an upstream proxy server failed and the
Web Proxy generated a core when the web server issued a 304 “Not Modified” response in
some cases. This no longer occurs. [Defect ID: 70141]

Fixed: Web Proxy generates a core file when the content length header does not equal
the amount of data being posted

Previously, the Web Proxy generated a core file when the content length header did not equal
the amount of data being posted. This no longer occurs. [Defect ID: 70671]

Fixed: Uploads hang when the server replies with a 500 Internal Server Error response in
some cases

Previously, uploads hung when the server replied with a 500 Internal Server Error response
because the Web Proxy never sends the 500 response to the client. This no longer occurs.
[Defect ID: 70997]

Fixed: Uploads to some servers fail

Previously, uploads failed when the web server sent a response body too early. This no longer
occurs. [Defect ID: 71236]

Robustness Fixes for Lockups on S160 Appliances

AsyncOS 6.3.4 includes a series of robustness fixes and logging enhancements to address
lockups that have occurred on S160 appliances. [Defect ID: 68955]

Fixed: Gateway Timeout errors occur for certain websites when HTTPS Proxy is enabled

Previously, when the HTTPS proxy was enabled, if an HTTPS website spontaneously closed
an HTTPS connection, gateway timeout errors sometimes occurred. This no longer occurs.
[Defect ID: 70547]

Fixed: Web Security appliance stopped unexpectedly when performing certain native
FTP transactions

Previously, when attempting to perform a native FTP transaction, if the user name included an
‘@’ but there was no proxy user password, core files were sometimes generated and the
appliance stopped unexpectedly. This no longer occurs. [Defect ID: 55033]

Fixed: DLP fails when both external DLP and IP spoofing are configured

Previously, when the Web Security appliance was configured for both External DLP and IP
spoofing, the appliance used the spoofed IP address to connect to the DLP server. This caused
the connection to fail and prevented a DLP verdict from being generated. This no longer
occurs. [Defect ID: 69792]