We're experiencing an issue setting up a basic ARR scenario. Here's our setup:
Only one drive/folder for caching, pointed to the OS partition.
Two websites setup. The Default website that comes standard with IIS. Another site using two host headers (headers sitea1, sitea2).
A single Default.htm file within the sitea1 website.
ARR Cache Configuration using defaults.
Cache Control Rules:
Apply rule: Always
Cache Duration: 10
Host: sitea1
Url: Default.htm
Server Proxy Settings:
Enable Proxy: Checked
Query string support: Include query string
All else defaults.
Examining the url rewrite rule that comes from setting up the Cache-Control rule you can see that the action is set to "None". Attempting to request a page using the rule established by the Cache-Control part of the UI (with action set to None) does nothing. No Cache-Control value is set when the action is None.
However, when you set the Action to Rewrite and simply rewrite the Url to a different hostheader (required otherwise you'll end up in an infinite loop) it seems to work fine (ie. including the appropriate cache-control header).
Any suggestions on how to correctly configure this non-web farm scenario without having to rewrite the requests?
Some additional questions are:
Which app pool does ARR run under? This seems to be undocumented.
Which permissions are needed to set up the ARR disk cache folder (based on which app pool)? This seems to be undocumented.
Thanks,
Jeff