I found that all of the responses on this page even now had difficulties. In particular, I seen that none of these would stop IE8 from utilizing a cached version from the page once you accessed it by hitting the back button.

Our investigations have shown us that not all browsers respect the HTTP cache directives inside a uniform fashion.

Using the pragma header within the response is often a wives tale. RFC2616 only defines it as being a request header

seven @Accountant: in his scenario, the user had logged out. Who will guarantee that the subsequent human consumer on that Person-Agent might be the person who just logged out?

This hack apparently breaks the back-ahead cache in Safari: Is there a cross-browser onload event when clicking the again button?

Anders SandvigAnders Sandvig 21k1616 gold badges6161 silver badges7474 bronze badges one 1 Placing a long-in the past Last-Modified has no influence on caching, other than permitting a cached reaction be used longer as a result of heuristic revalidation.

Despite the discussion in remarks here, this is sufficient to disable browser caching - this causes ASP.Web to emit response headers that tell the browser the document expires immediately:

Why is the number of Marie Curie postdoctoral fellowships in mathematics significantly lower than in other subjects?

seven Usually do not install this bundle to save 4 lines of code. Cutting down dependencies ought to normally be considered one of your ambitions. Every dependency you insert is another thing website that needs for being up to date, another way to get your project hacked, another way to incorporate even more dependencies if this offer provides dependencies, and many others.

Nevertheless, cacheing headers are unreliable in meta features; for a single, any web proxies between the site along with the consumer will entirely disregard them. You ought to often make use of a real HTTP header for headers which include Cache-Control and Pragma.

I have attempted various combinations and had them are unsuccessful in FireFox. It's been a while so the answer higher than may possibly work fine or I may have missed a little something.

Joseph ConnollyJoseph Connolly 9451111 silver badges2121 bronze badges two one For Website.config I'd modify just a little bit to apply the custom headers only for anyone scripts which we know are loaded dynamically / using requirejs. Assuming your scripts are present in client folder: .....

I edited configuration file of my project to append no-cache headers, but that also disabled caching static information, which isn't ordinarily desirable.

For those who need to override the defaults from the NoCacheController class, just specify the cache options on your action process along with the settings on your Action method will take precedence.