Cisco Cisco Web Security Appliance S680 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
35
Fixed: Packet capture feature fails to include some packets
Previously, the packet capture feature failed to include packets sent to the Web Security
appliance using GRE. This made it more difficult for Customer Support to assist customers.
This no longer occurs. [Defect ID: 48971]
appliance using GRE. This made it more difficult for Customer Support to assist customers.
This no longer occurs. [Defect ID: 48971]
Fixed: End-user acknowledgement page link contains client IP instead of Web Security
appliance IP after DNS failure
appliance IP after DNS failure
Previously, the link included in the end-user acknowledgement page contained the client IP
address instead of Web Proxy IP address after DNS failure. This no longer occurs. [Defect ID:
49114]
address instead of Web Proxy IP address after DNS failure. This no longer occurs. [Defect ID:
49114]
Fixed: Some FTP over HTTP requests erroneously time out when the network connection
is slow
is slow
Previously, some FTP over HTTP requests mishandled server responses and erroneously timed
out client connections when the network connection was slow. This no longer occurs. [Defect
ID: 49142]
out client connections when the network connection was slow. This no longer occurs. [Defect
ID: 49142]
Fixed: Configuration file erroneously references deleted custom URL categories in some
cases
cases
Previously, when a custom URL category was deleted and the Web Security appliance
configuration was saved, the configuration file included references to the deleted category if
the category was used in a time-based Access Policy. This no longer occurs. [Defect ID:
49416]
configuration was saved, the configuration file included references to the deleted category if
the category was used in a time-based Access Policy. This no longer occurs. [Defect ID:
49416]
Fixed: Access logs and FTP logs do not include entries for blocked native FTP
transactions that require authentication when the client provided no credentials
transactions that require authentication when the client provided no credentials
Previously, the access logs and FTP did not include entries for blocked native FTP transactions
that required authentication when the client provided no credentials. This no longer occurs.
[Defect ID: 49859]
that required authentication when the client provided no credentials. This no longer occurs.
[Defect ID: 49859]
Fixed: Cannot access URL Categories page from the Advanced section of Access Policies
using Internet Explorer 7
using Internet Explorer 7
Previously, when you clicked the URL Categories link in the Advanced section of an Access
Policy using Internet Explorer 7, the page showing the authentication groups appeared instead
of the URL Categories page. This no longer occurs. [Defect ID: 50152]
Policy using Internet Explorer 7, the page showing the authentication groups appeared instead
of the URL Categories page. This no longer occurs. [Defect ID: 50152]
Fixed: Web Proxy generates a core file when processing some transparent authentication
requests
requests
Previously, the Web Proxy generated a core file when processing some transparent
authentication requests. This no longer occurs. [Defect ID: 50198]
authentication requests. This no longer occurs. [Defect ID: 50198]