Cisco Cisco Web Security Appliance S390
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
53
Web Proxy erroneously does not recognize some root authorities
By default, the Web Proxy erroneously does not recognize the “VeriSign Class 3 Secure Server
CA” root certificate. The Web Proxy does not recognize the root authority of websites that use
this root certificate to establish its trust relationship. Depending on how the HTTPS Proxy is
configured to handle invalid certificates, client requests to these sites may be dropped.
CA” root certificate. The Web Proxy does not recognize the root authority of websites that use
this root certificate to establish its trust relationship. Depending on how the HTTPS Proxy is
configured to handle invalid certificates, client requests to these sites may be dropped.
Workaround: Import the “VeriSign Class 3 Secure Server CA” root certificate as a custom root
authority certificate on the Security Services > HTTPS Proxy page. [Defect ID: 70537]
authority certificate on the Security Services > HTTPS Proxy page. [Defect ID: 70537]
PAC file hosting does not work with a configured VLAN
When a VLAN is configured on the P1 network interface, and you host a PAC file on the Web
Security appliance, AsyncOS only listens for PAC file requests on the P1 interface IP address,
not the VLAN IP address. [Defect ID: 71992]
Security appliance, AsyncOS only listens for PAC file requests on the P1 interface IP address,
not the VLAN IP address. [Defect ID: 71992]
Web Proxy erroneously drops CONNECT requests to ports other than port 443 in some
cases
cases
When you add a port other than port 443 to the Transparent HTTPS Ports field on the Security
Services > HTTPS Proxy page, the Web Proxy erroneously drops CONNECT requests to that
port.
Services > HTTPS Proxy page, the Web Proxy erroneously drops CONNECT requests to that
port.
Workaround: After adding the port to the Transparent HTTPS Ports field, edit any Access
Policy and submit and commit the changes. [Defect ID: 66309]
Policy and submit and commit the changes. [Defect ID: 66309]
Some DNS related CLI commands do not have any effect
The following
advancedproxyconfig > DNS
CLI commands do not have any effect:
• Enter the time to cache successful DNS results if DNS does not provide TTL (in seconds).
• Enter the time to cache results of DNS errors (negative DNS caching) (in seconds).
The Web Proxy currently ignores the values you enter for these commands and applies the
default values used by the DNS server configured. [Defect ID: 55329]
default values used by the DNS server configured. [Defect ID: 55329]
WCCP Module Logs contain no information
The WCCP Module Logs contain no information.
Workaround: Read the Default Web Proxy Logs and search for the string “wccp” for
information related to WCCP. [Defect ID: 56254]
information related to WCCP. [Defect ID: 56254]
Exported URL Categories Report does not show all information
When you click the Export link on the Monitor > URL Categories page, the exported .csv file
does not contain any information in the “bandwidth saved by blocking” column. [Defect ID:
56418]
does not contain any information in the “bandwidth saved by blocking” column. [Defect ID:
56418]