Cisco Cisco Web Security Appliance S160 User Guide
15-19
Acknowledgements. This setting applies to users tracked by username and
users tracked by IP address. You can specify any value from 30 to 2678400
seconds (one month). Default is 1 day (86400 seconds).
users tracked by IP address. You can specify any value from 30 to 2678400
seconds (one month). Default is 1 day (86400 seconds).
Inactivity Timeout. The Inactivity Timeout determines how long a user
tracked and acknowledged by IP address (unauthenticated users only) can be
idle before the user is no longer considered acknowledged. You can specify
any value from 30 to 2678400 seconds (one month). Default is four hours
(14400 seconds).
tracked and acknowledged by IP address (unauthenticated users only) can be
idle before the user is no longer considered acknowledged. You can specify
any value from 30 to 2678400 seconds (one month). Default is four hours
(14400 seconds).
Custom message. The custom message is text you enter that appears on every
end-user acknowledgement page. You can include some simple HTML tags
to format the text. For example, you can change the color and size of the text,
or make it italicized. See
end-user acknowledgement page. You can include some simple HTML tags
to format the text. For example, you can change the color and size of the text,
or make it italicized. See
more information.
You can only include a custom message when you configure the end-user
acknowledgement page in the web interface, versus the CLI.
acknowledgement page in the web interface, versus the CLI.
Consider the following rules and guidelines when enabling the end-user
acknowledgement page:
acknowledgement page:
When a user is tracked by IP address, the appliance uses the shortest value for
maximum time interval and maximum IP address idle timeout to determine
when to display the end-user acknowledgement page again.
maximum time interval and maximum IP address idle timeout to determine
when to display the end-user acknowledgement page again.
The first transaction from a user must be an HTTP request, and the user must
agree to the terms for all transactions to succeed. If users try to send an
HTTPS or native FTP request before an HTTP request, the HTTPS or native
FTP request fails.
agree to the terms for all transactions to succeed. If users try to send an
HTTPS or native FTP request before an HTTP request, the HTTPS or native
FTP request fails.
When the Web Proxy restarts, the Web Proxy considers all users to have timed
out, and it displays the end-user acknowledgement page again. The Web
Proxy may restart based on different events, such as when the Default Proxy
Log subscription changes or when changes are made to the global
authentication settings or FTP Proxy settings.
out, and it displays the end-user acknowledgement page again. The Web
Proxy may restart based on different events, such as when the Default Proxy
Log subscription changes or when changes are made to the global
authentication settings or FTP Proxy settings.
When the appliance is deployed in explicit forward mode and a user goes to
an HTTPS site, the end-user acknowledgement page includes only the
domain name in the link that redirects the user to the originally requested
URL. If the originally requested URL contains text after the domain name,
that text is truncated.
an HTTPS site, the end-user acknowledgement page includes only the
domain name in the link that redirects the user to the originally requested
URL. If the originally requested URL contains text after the domain name,
that text is truncated.