Cisco Cisco Web Security Appliance S160 Notas de publicación
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
17
B U G S F I X E D I N 6 . 3 . 5
Fixed: Some client applications cannot communicate with the Web Proxy with NTLMSSP
authentication enabled
authentication enabled
Previously, some client applications could not communicate with the Web Proxy when
NTLMSSP authentication was enabled. This no longer occurs. [Defect ID: 72670]
NTLMSSP authentication was enabled. This no longer occurs. [Defect ID: 72670]
Fixed: Uploads fail when the connection between the Web Proxy and the destination
server is slower than the connection between the Web Proxy and the client
server is slower than the connection between the Web Proxy and the client
Previously, uploads failed when the connection between the Web Proxy and the destination
server was slower than the connection between the Web Proxy and the client. This no longer
occurs. [Defect ID: 72817]
server was slower than the connection between the Web Proxy and the client. This no longer
occurs. [Defect ID: 72817]
Fixed: Global policies are erroneously assigned to native FTP transaction when
authentication is used in some cases
authentication is used in some cases
Previously, the Global Access and Global Routing Policies were assigned to native FTP
transactions instead of the proper user-defined Access and Routing Policies when the assigned
Identity used authentication and IP address surrogates. This no longer occurs. [Defect ID:
72485]
transactions instead of the proper user-defined Access and Routing Policies when the assigned
Identity used authentication and IP address surrogates. This no longer occurs. [Defect ID:
72485]
Fixed: Web interface does not allow an empty value for the Base DN property in LDAP
authentication realms
authentication realms
Previously, the web interface did not allow an empty value for the Base DN property in LDAP
authentication realms. This no longer occurs. [Defect ID: 71284]
authentication realms. This no longer occurs. [Defect ID: 71284]
Fixed: Native FTP transactions are delayed when using an upstream proxy in some cases
Previously, when the appliance used an upstream proxy server and an FTP client sent multiple
native FTP transactions in succession, the transactions were delayed due to the appliance
mismanaging connections to the proxy server and to the client. This no longer occurs. [Defect
ID: 71931, 72018]
native FTP transactions in succession, the transactions were delayed due to the appliance
mismanaging connections to the proxy server and to the client. This no longer occurs. [Defect
ID: 71931, 72018]
Fixed: Clients cannot access files with the “#” character using FTP over HTTP
Previously, clients could not access files with the “#” character using FTP over HTTP because
the Web Proxy did not URL encode the “#” character. This no longer occurs. Now, the Web
Proxy URL encodes the “#” character when returning the FTP directory list to the client
application. [Defect ID: 72211]
the Web Proxy did not URL encode the “#” character. This no longer occurs. Now, the Web
Proxy URL encodes the “#” character when returning the FTP directory list to the client
application. [Defect ID: 72211]
Fixed: An internal process runs out of memory and generates a core file when creating
time-based Decryption Policies in some cases
time-based Decryption Policies in some cases
Previously, an internal process ran out of memory and generated a core file when creating
multiple time-based Decryption Policies. This no longer occurs. [Defect ID: 72254]
multiple time-based Decryption Policies. This no longer occurs. [Defect ID: 72254]