IIS7 - UI & Remote Management

Re: How to set cache control for static content

anilr — Thu, 16 Jul 2009 01:13:20 GMT

Yes, see http://www.iis.net/ConfigReference/system.webServer/staticContent/clientCache for examples.

Re: How to set cache control for static content

pure.krome — Fri, 12 Jun 2009 02:07:33 GMT

Anilr, is it possible to set the cache control, for specific folders in a website, programatically in a web.config?

eg. I wish to add a max-age for

/images
/css
/javascript

can this be done in a web.config file?

Re: How to set cache control for static content

anilr — Wed, 10 Dec 2008 22:49:00 GMT

This setting only controls client caching of the static content - so anything you do at the server will not purge the cache - the cache has to be purged at the client.

Re: How to set cache control for static content

caslar4711 — Mon, 08 Dec 2008 14:59:53 GMT

Well. Thanks for great information. I have a question though:

If I enabled static filecaching on a specific directory, i.e:

appcmd.exe set config "Default Web Site/images" -section:system.webServer/staticContent -clientCache.cacheControlMode:UseMaxAge

Then, how am I able to remove it again ?

The funny thing is, I have a .css file in a directory where I did the exact thing above, and max age is set to 84600, but even its the 8. december today, and I make sure my temporary Internet Files etc. is deleted, my browser still sees this .css file as being from the 28. november, even the file is build today. This really worries me, as I see no way to get around this, recycling application pools or not.

Any help is really appreciated.

Best, Lars

Re: How to set cache control for static content

afjk — Sun, 05 Oct 2008 22:36:43 GMT

Thanks! Hopefully this info will help reduce the load on my webserver .. its starting to get a bit overstressed!

AF

Re: How to set cache control for static content

andrewbi — Wed, 03 Sep 2008 18:15:20 GMT

Recycling the app pool will destroy any session variables for ASP.NET applications running in that particular app pool but will leave other apps running in other app pools alone.

Re: How to set cache control for static content

theadmirableone — Sat, 30 Aug 2008 18:06:02 GMT

Well Anil.R you are correct! :~) Hats-off to you!

After so many days of trying to get this to work without reseting IIS, your suggestion works.

The remaining question is: If I use your suggested process/command after creating a distinct app pool for this particular web app, (so that the other app pools are not effected), does this command also destroy the session variables that the IIS7 might be currently using, in production, or does it simply clear the cache?

thanks a million, theadmirableone

Re: How to set cache control for static content

anilr — Fri, 29 Aug 2008 20:28:08 GMT

Disabling caching of ISAPIs has not been supported since IIS6.

What you were ending up doing on IIS5.1 is to load and unload all of asp.net and .net framework (and the asp.net worker process) after every request. You can achieve the same effect by recycling the application pool when you want by running

%windir%\system32\inetsrv\appcmd.exe recycle apppool "DefaultAppPool" (replace name of app-pool you want)

Re: How to set cache control for static content

theadmirableone — Thu, 28 Aug 2008 15:08:54 GMT

Anilr,

Let me be clear about what I am trying to do.

Let's suppose that caching ISAPI is enabled for a particualt web app. on the IIS 5.1. If I place a .dll in the GAC and then call it from that web application in ASP.NET 2.0, then all is fine.

However, if I go to rebuild that .dll from within ASP.NET 2.0 to return a different hard coded string, and then replace the original .dll in the GAC, (effectively replacing the oringinal .dll with the same assembly version and build), IIS does not see the different string when I call the .dll because it caches the .dll. That is why I use: "cscript.exe adsutil.vbs set w3svc/1/root/myWebApp/cacheisapi 0" (without quotes), to disable the ISAPI cache. When this is done, and IIS is reset, IIS 5.1 does not cache the .dll in the GAC anymore. This means that when no matter how "many" times I rebuild my .dll in ASP.NET 2.0 with different hard coded strings to return and place that new .dll in the GAC, (with the same assembly version and build), the new string will always show when that .dll is being called from any app. This is becuase caching is turned off at the ISAPI level.

I have tried this scenario dozens of times, and it certainly resolves the issue of replacing the same .dll in the GAC, (with the same assembly version and build), and still getting the new hard coded string, simply becuase the Cache ISAPI was turned off for that particular website.

If I were to leave the cache ISAPI on, then IIS caches the .dll and will never retrieve the new string, even after I rebuild my ASP.NET 2.0 .dll and replace it in the GAC with same assembly and version.

I could use a differenct assembly and build version, instead of turning off the ISAPI cache to resolve it, however I would like to use the same (assembly and build version).

So the question I pose to you is: how do I turn off ISAPI cache in IIS7, as "cscript.exe adsutil.vbs set w3svc/1/root/myWebApp/cacheisapi 0" (without quotes), does nothing for me in IIS 7?

thanks ahead of time, theadmirableone

Re: How to set cache control for static content

anilr — Tue, 26 Aug 2008 21:27:52 GMT

This thread was about caching of responses on the client - you are talking about dlls on the server in memory - also, ISAPI extensions in the GAC does not make any sense.

Re: How to set cache control for static content

theadmirableone — Mon, 25 Aug 2008 04:20:56 GMT

Hello Anilr,

I am totally frustrated at this caching deal.

I was originally using IIS 5.1 on Windows XP. To turn the Cashe ISAPI applications

check box off from the command line prompt, I would type in

cscript.exe adsutil.vbs set w3svc/1/root/myWebApp/cacheisapi 0

This would effectively turn off the IIS caching, and so when I replace the DLL file in the GAC, (Global Assembly Cache), the change would take effect right away. This means the IIS 5.1 was not cashing the dll in memory. This worked great! So now I have the ability to replace the DLL in the GAC and the IIS server would serve the fresh content right away without having to reset IIS. However this line does "not" work as far as I have tried in IIS 7.0.

I tried your suggestion of this as well from the command line prompt, for IIS 7.0:

appcmd set config "Default Web Site/myWebApp" -section:system.webServer/caching -enabled:false

and it returned:

"Applied configuration changes to section......."

So it executes, but still does not prevent caching of the DLL. I would like to mimik the same thing I had for IIS 5.1 (in win-xp) for IIS 7.0 (in VISTA), but have spent endless hours wondering how to get it done. If your suggestion works, I should be able to reoplace a DLL in the GAC with the same name, version and build, and IIS should "not" cache it, therefore allowing the webpage that utilizes that DLL in the GAC to reflect any new changes instantly. It works in win-xp, so why does it not work in vista?

**Please help!.... Thanks in advance,

theadmirableone

Re: How to set cache control for static content

jimrPA — Wed, 16 Jul 2008 21:25:36 GMT

that's it, thanks

Re: How to set cache control for static content

anilr — Wed, 16 Jul 2008 17:42:18 GMT

Are you talking about server-side caching or client-side caching? The posts above already talk about client-side caching, for server-side caching, you can do the following

appcmd set config "My Site" -section:system.webServer/caching -enabled:false

Re: How to set cache control for static content

jimrPA — Sat, 12 Jul 2008 16:23:56 GMT

Is there a way to disable static caching on a site level? Or set the caching period for the entire site and not each folder?

Re: How to set cache control for static content

Galcho — Wed, 27 Feb 2008 19:40:20 GMT

here is a further research on the subject: IIS7: How to set cache control for static content?

Hope this helps