با سلام
دوستان نحوه راه اندازی کش رو در TMG می فرمایند گویا با آیزا تفاوت داره نتونستم راه اندازی کنم.
ممنون
با سلام
دوستان نحوه راه اندازی کش رو در TMG می فرمایند گویا با آیزا تفاوت داره نتونستم راه اندازی کنم.
ممنون
Content Caching with Forefront Threat Management Gateway (TMG) 2010
Enabling Content CachingContent caching can be enabled and configured using the Web Access PolicyWizard, which can be run once theGetting Started Wizard has completed.
Figure 1
If you elected not to use the Getting Started Wizard to configure TMG, open the TMG management console and highlight Web Access Policy, then click Configure Web Access Policy.
Figure 2
When prompted by the Web Access Policy Wizard, select the option to Enable the default Web caching rule, and then click Cache Drives….
Figure 3
The only requirement for enabling content caching is having at least one NTFS formatted volume on which to store the cache file. Highlight the volume you wish to store the cache file on, and then specify the maximum size of the cache in megabytes (MB). It is generally recommended that you allocate a minimum of 100MB in addition to .5MB for each Web Proxy client using the system.
Figure 4
The content cache can be up to 64GB per volume. You can specify multiple cache files on additional volumes, if required. For optimal cache performance, best practices dictate that you store the cache file on a volume that does not contain the system partition.
Cache Rules
Caching is implemented using Cache Rules, which function much the same as firewall policy rules. You can view, edit, and add rules by clicking the Web Caching: link in the Web Access Settings window.
Figure 5
Select the Cache Rules tab and you will see an ordered list of rules that ends with a Default rule. Each cache rule is evaluated in order from top to bottom, with the first rule that matches the request being processed. This is an important point to remember to prevent unexpected cache rule processing.
The Web Access Policy Wizard automatically creates a cache rule that works well in most cases. To view the properties of this rule, highlight the rule and choose Edit…. On the General tab you will find that the rule is enabled, and on the To tab the destination is the External network, indicating that this rule will apply to any request made to theExternal network.
Figure 6
The Cache Store and Retrieval tab defines explicitly if and how to cache the requested content. You can control what content is retrieved from the cache and what to do with requests for objects that are not currently cached, and you can choose the option to cache dynamic content, content for offline browsing, and content requiring user authentication.
Figure 7
The HTTP tab is used to enable and configure HTTP caching. Here we can specify how long objects will live in the cache.
Figure 8
The FTP tab is used to enable and configure FTP object caching. Here we can specify how long objects downloaded via FTP will live in the cache.
Figure 9
The Advanced tab is used to configure a limit on the size of objects in cache. This will prevent large downloaded files from consuming excess amounts of cache. In addition there is an option to Cache SSL responses. This applies only to bridged SSL traffic from web publishing rules. The TMG firewall does not cache SSL responses in forward (outbound) proxy scenarios.
Figure 10
Cache Exceptions
On rare occasion you may encounter a web site that does not work well with a caching proxy server. To prevent content from a particular web site from being cached, create a new cache rule that applies only to the specific destination in question.
Figure 11
Select the option Never, no content will ever be cached.
Figure 12
Make certain to place this cache exception rule first in the ordered list of cache rules. This will prevent another cache rule from matching before the exception rule, causing the content to be cached unexpectedly.
Figure 13
ویرایش توسط alimohamadi : 2012-01-28 در ساعت 02:50 AM