01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6<br />

<strong>Web</strong> filtering<br />

Supporting functions<br />

Bandwith throttling rule for downloads<br />

The following is an example of a rule that can execute bandwidth throttling rule for downloads.<br />

Note: The example shows approximately how the rule appears on the user interface.<br />

Name<br />

Limit download speed for media types on throttling list<br />

Criteria Action Event<br />

MediaType.EnsuredTypes at least one in list MediaType<br />

Throttling List<br />

–> Continue – Throttle.Server (1000)<br />

The rule uses the Throttle.Server event to limit the speed with which downloads are performed to 1000<br />

Kbps if the web object that should be downloaded belongs to a media type on a particular list.<br />

In the criteria of the rule, the MediaType.EnsuredTypes property is used to detect the media type of the<br />

web object that the web server sends. An object can also be found to belong to more than one type.<br />

If any of these types is on the Media Type Throttling List, the criteria is matched and the rule applies.<br />

The throttling event is then executed.<br />

The Continue action lets rule processing continue with the next rule.<br />

Bandwidth throttling rules and rule sets<br />

It is recommended that you create an overall rule set for bandwidth throttling rules and embed two rule<br />

sets in it, one for throttling uploads and another for throttling downloads. You can then let the<br />

embedded upload rule set apply for the request cycle and the embedded download rule set for the<br />

response cycle.<br />

Note: Within each embedded rule set, you can have multiple throttling rules that apply to different kinds of<br />

web objects.<br />

The overall rule set for bandwidth throttling should be placed at the beginning of your rule set system.<br />

If this is not done, rules in other rule sets can start unthrottled downloads of web objects before your<br />

throttling rules are executed.<br />

For example, a rule for virus and malware filtering could trigger the download of a web object that has<br />

been sent by a web server in response to a user request. The web object then needs to be completely<br />

downloaded to the appliance to see whether it is infected. If your bandwidth throttling rule set is placed<br />

and processed after the rule set with the virus and malware filtering rule, bandwidth throttling is not<br />

applied to that download.<br />

232 <strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!