[SOLVED] Invalidate browser cache


I have a question related to cache invalidation techniques… I am trying to implement a mechanism for my website, that automatically invalidates browser cache (css, images…). I want to be able to programatically invalidate browser cache, whenever I update the website (change images or styles);

For example: for the current release, among others, the css and some of the images have changed. In this situation I want that after the update is finished, when a user performs a request to the website, his browser’s cache to get automatically invalidated, thus forcing the re-download of the new images and styles. This should be done only for the client’s first request… the following ones should be retrieved from cache (so setting the no-cache pragma is out of the question).

Here’s what i’ve tried:
in the BeginRequest event handler, I added the following lines:


this sets the ETag in the response headers. I figured that if I change this ETag at each release, and set it at each request, the cache will be invalidated, but it seems that it is not. I used Live HTTP headers to see the results and the ETAG is correctly set up for the response, but the css and images are still taken from cache.

Any ideas of how I could accomplish this, or if it can be accomplished at all?


I have run into issues like this in the past. Unfortunately I couldn’t find a really nice way to accomplish this so I had to come up with a workaround. I was only dealing with this issue for CSS files so I added an extra querystring parameter to every CSS reference, for example

 <link rel="stylesheet" type="text/css" 
       href="default.css?buildnumber=<%= Buildnumber %>" />

The build number gets incremented with each release so the browser was forced to go look for this new file. Not an ideal solution, but it worked without a hitch.

Answered By – Bob

Answer Checked By – Candace Johnson (BugsFixing Volunteer)

Leave a Reply

Your email address will not be published. Required fields are marked *