Cisco Cisco Web Security Appliance S170 사용자 가이드

All combinations of URL paths and domain names in embedded links within custom text and the custom 
logo in on-box end-user notification, end-user acknowledgement, and end-user URL filtering warning 
pages are exempted from the following:

User authentication

End-user acknowledgment

All scanning, such as malware scanning and web reputation scoring

For example, if the following URLs are embedded in custom text:

http://www.example.com/index.html

 

http://www.mycompany.com/logo.jpg

 

Then all of the following URLs will also be treated as exempt from all scanning:

http://www.example.com/index.html

 

http://www.mycompany.com/logo.jpg

 

http://www.example.com/logo.jpg

 

http://www.mycompany.com/index.html

 

Also, where an embedded URL is of the form: 

<protocol>://<domain-name>/<directory path>/

 then 

all sub-files and sub-directories under that directory path on the host will also be exempted from all 
scanning. 

For example, if the following URL is embedded: 

http://www.example.com/gallery2/

 URLs such as 

http://www.example.com/gallery2/main.php

 will also be treated as exempt.

This allows administrators to create a more sophisticated page with embedded content so long as the 
embedded content is relative to the initial URL. However, administrators should also take care when 
deciding which paths to include as links and custom logos.

Users accessing the Internet sometimes cannot access the server they want. By default, the Web Proxy 
displays a notification page informing users they were blocked and the reason for the block. This section 
lists and describes all possible notification pages a user might see while accessing the Internet.

Possible reasons that cause notification pages to appear include the following:

End-user notification pages are enabled and the user accessed the Internet in a way that violated an 
Access Policy.

End-user notification pages are configured to allow end-users to report misclassified pages to Cisco 
and the user reported a misclassified page.

The end-user acknowledgement page is enabled and the user accessed the Internet for the first time 
since the timeout period expired.

The HTTPS Proxy is enabled and the appliance is configured to drop HTTPS requests to servers 
with invalid certificates.

The Web Security appliance could not access the server requested due to an external error, such as 
DNS failure or an unavailable server.