The anti-leeching can be done using URL rewrite (which is installed with ARR). tip #6 http://ruslany.net/2009/04/10-url-rewriting-tips-and-tricks/

Since installing the ARR v2 RC I am periodically receiving warning events that the ARR disk cache directory is unhealthy. "Drive with path '\\?\path' is being marked unhealthy. The data contains the error code." Provider: Application Request Routing EventID: 1006 [ Qualifiers] 32768...

It's difficult to make a blanket recommendation on CPU/memory without knowing the traffic pattern of your usage. As you may have guessed, the first bottleneck that you are going to hit is disk i/o. Depending on the average size of the files that are being cached, you may or may not be able to saturate...

Jim You are absolutely right. We did change the default setting from 5 to 60 seconds. We made this change with the CDN customers in mind where 5 second caching was simply too short (ie. Publicly available Internet contents that are cache-able don't really change every 5 seconds. And by keeping it...

I have just installed the ARR v2 RC and wanted to ask a questions that I did not bother with during the beta. In the Application Request Routing Cache form the health status of my primary drive appears as Unknown with an Alert of "Disk Utilization is not available because the worker process is not...

I would like to understand how ARR disk caching works with ASP.Net applications and have not been able to find a good reference. I have a simple testing server farm configuration with a single ARR server and a few content servers. Everything with my ASP.Net application is caching appropriately, static...

With memory (and in conjuction with disk), it works slightly differently. Let me see if I can clarify. Let's suppose that the memory cache interval is set to 5 seconds (default value.) The flow would be something like: 1) Request is received by Windows server (http.sys, actually). 2) Cache miss at...

Won, Thanks that was great. To carry over an idea from our other thread ( http://forums.iis.net/t/1160295.aspx ) I assume that irrespective of whether the object is cached in memory or disk, the object invalidation process with be the same. The cached object will always be served to the requesting user...

I assume the prescribed solution for this condition, might be create a Global URL rewrite rule on the ARR server that redirects input for a blank URL explicitly to the default page. If that rule processes before the ARR Cache Control rule then I would think you would get the same behaviour for the default...

Jim The memory cache is done at the kernel level. You could have a netmon between ARR and the content server to see if you actually see the cache hit. A simpler way would be to type the following on an elevated command prompt (which will show you what's stored in kernel cache.) netsh http show cache...