Grado III: a todos se les debería realizar radiología ánteroposterior y lateral, y
MUSCULATURA DEL CUELLO
7. MATERIALES Y MÉTODOS
7.6. Análisis Estadístico
This action displays a notification page in the user’s Web browser. A user must read the notification and click an Accept button before being allowed to access the Web content. You can customize the following:
❐ The page title, notification message, and the Accept button.
❐ The conditions that cause a notification to be displayed again. By default, the notification is displayed each time a user begins a new Web browsing session (reboots, logs out, or closes all Web browser windows). You can configure re- notification to occur for each new visited host or Web site, or after a time interval.
1 2
3
This feature is designed to provide the following functionality:
❐ Web-use compliance: A compliance page is a customized notification page displayed on a user’s Web browser when attempting to access the Internet. This page ensures employees read and understand the company’s Acceptable Use Policy before Internet use is granted. Typically, a compliance notification is displayed each time a browser is opened, but you can configure a time condition to display the page at specific intervals or times of the day, week, or month.
❐ Coach users: A coaching page displays when a user visits a Web site that is blocked by content filtering policy. This page explains why the site is blocked, the consequences of un-authorized access, and a link to the site if business purposes warrants access. A coaching page is configured to display each time a user visits a new Web page that is barred by content filtering policy; however, you can also configure this page to appear at different time intervals.
To configure HTML notification:
1. In the Name field, enter a name for the object or leave as is to accept the default. 2. In the Title field, enter a name that is the title of the page (text only; no HTML is
allowed).
3. In the Body field, compose a block of HTML that displays the message to the user. You can also customize the Accept link or button text. The HTML body must contain an
Accept button or link. The default is:
1 2 3 4 5
<body><a href="$(exception.details)" onclick="Accept();">Accept</ a></body>
You can also use a button image (the image resides on an external Web server, as in the following example:
<body><a href="$(exception.details)" onclick="Accept();"> <img src=”http://server.com/images/accept.png”> </a> </body>
If you use an HTML editor to compose code, you can paste it into the VPM; however, only copy the HTML from the <body> tag to the </body> tag.
4. Under Notify mode, select an option that determines notification when visiting a new Web site:
• Notify once for all hosts—The notification page is displayed only once; this is used for configuring compliance pages. This option uses a Virtual Notify URL. If you must change the URL from the default value, please read the limitation section following this procedure.
• Notify only once for related domains—The notify page reappears each time the user visits a new Web site; this is used for configuring coaching pages.
• Notify on every host—The notify page reappears each time the user visits a new Web host. Blue Coat recommends that only highly experienced administrators employ this option. In addition to breaking banner ads, as described above in the previous option, this option, on some Internet Web sites, might cause Javascript errors that impair the functionality of the site.
5. Under Notify users again, select an option that specifies when the notification expires and re-notification is required:
• At next browser session— The notification page does not reappear until the next browser session. When a user reboots, logs out, or closes all Web browser windows, this ends the browser session.
• After (time interval)—Notification reoccurs after the defined elapsed time
Note: This option might cause users to experience some noticeable Web browsing slowness.
Note: This option interferes with some Web advertising banners. In some cases, the notification page appears inside the banner. In other cases, banner ads are disabled by javascript errors. To fix these problems, do not serve notification pages for URLs that belong to the Web Advertising, Advertising, or Web Ads
category. The actual name of this category varies with the content filtering vendor, and some vendors do not have an equivalent.
The above example creates a Notify Object with a custom message, set to display once a day after 7 AM.
Interactivities and Workarounds
If you must change the default Virtual Notify URL, consider the following:
❐ The Virtual Notify URL consists of an HTTP domain name or IP address (http://); a
port number is optional.
❐ Do not use a host name that is explicitly defined as a trusted site on Internet Explorer 6 for Windows XP, Service Pack 2. Furthermore, only use domain names that contain dots. If you use domain names that do not contain dots, the HTTP redirects generated by the notification action causes Internet Explorer to display false warning messages each time the user is redirected from an untrusted site to a trusted site, or the other way around.
❐ For transparent proxy deployments, the domain name must be DNS-resolvable to an IP address that is in the range of destination IP addresses that are routed to the SG appliance.
Policy Interactions
This action generates CPL that might interfere with other policy or cause undesired behavior. Enhancements will occur in future SGOS releases. For this release, consider the following guidelines:
❐ Do not create VPM policy that modifies the Cookie request header.
❐ Do not create VPM policy that modifies the Set-Cookie and P3P response headers. ❐ Notification pages exist in the browser history. Therefore, if you click Accept and are
taken to the requested page, then click the back button, you get the notification page again.
❐ If you have a chain of SG appliances, with different notification pages configured on each appliance in the chain, then each notification page must have a different object name.