Cisco Cisco Web Security Appliance S170 릴리즈 노트
56
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
Workaround: Use the
smtprelay
CLI command to configure an SMTP relay host. [Defect ID:
51811]
Deleting directories on the appliance causes errors when saving or loading a
configuration file or when upgrading AsyncOS for Web
configuration file or when upgrading AsyncOS for Web
Errors occur under the following circumstances:
• An administrator connects to the Web Security appliance using FTP and deletes some
directories, such as directories that exist for holding log files.
• The configuration is saved or loaded, or AsyncOS for Web is upgraded.
Workaround: Recreate all missing directories on the appliance before saving or loading the
configuration file and before upgrading AsyncOS for Web. [Defect ID: 51514]
configuration file and before upgrading AsyncOS for Web. [Defect ID: 51514]
Incorrect response size value recorded in the access logs for FTP over HTTP transactions
when the transaction times out
when the transaction times out
An incorrect response size value is recorded in the access logs for FTP over HTTP transactions
when the transaction times out. The value should be zero (0) for the response size when a
transaction times out, but instead, the value appears as a large positive or negative number.
You can ignore the value stored in the access logs for the response size. [Defect ID: 51822]
when the transaction times out. The value should be zero (0) for the response size when a
transaction times out, but instead, the value appears as a large positive or negative number.
You can ignore the value stored in the access logs for the response size. [Defect ID: 51822]
Web Proxy erroneously adds its domain name as a DNS search domain in some cases
When a client explicitly forwards a request for a URL that does not exist, the Web Proxy
appends its own name domain to the URL and tries the DNS lookup again. For example, the
Web Security appliance host name is wsa.example.com, and a client sends a request to
appends its own name domain to the URL and tries the DNS lookup again. For example, the
Web Security appliance host name is wsa.example.com, and a client sends a request to
http://myhost.mysite. The original DNS lookup fails to find http://myhost.mysite, so the Web
Proxy tries another DNS lookup for http://myhost.mysite.example.com.
Proxy tries another DNS lookup for http://myhost.mysite.example.com.
Workaround: Configure the appliance to use transparent mode and transparently redirect
client requests to the Web Proxy. [Defect ID: 51864]
client requests to the Web Proxy. [Defect ID: 51864]
Changing the name of the Web Security appliance host name does not take effect
immediately
immediately
Changing the name of the Web Security appliance host name does not take effect
immediately.
immediately.
Workaround: Restart AsyncOS for Web, or contact Customer Support to restart the Web Proxy
only. [Defect ID: 51933]
only. [Defect ID: 51933]
Changing the default gateway does not display the new IP address in the web interface
immediately
immediately
When you change the default gateway and click Submit, the Network > Routes page does not
immediately display the new IP address for the default gateway after clicking Submit.
immediately display the new IP address for the default gateway after clicking Submit.
Workaround: Reload the page in the browser and the correct default gateway address
appears. [Defect ID: 52022]
appears. [Defect ID: 52022]