Browsers ought to validate freshness of cached stale written content in advance of utilizing it, but It isn't obligatory unless the additional directive ought to-revalidate is specified.
For what It truly is worth, I just needed to handle this in my ASP.NET MVC 3 software. Here will be the code block I used from the Global.asax file to handle this for all requests.
You can also decorate many of the actions with this attribute if you need them to become non-cacheable, in lieu of decorating the whole controller.
Even when you are applying nocache, the ETag header just isn't eliminated, since it works inside of a different way. It can be generated at the conclusion of the request and could be another source of unintended caching. So as to handle it you have two selections.
Also, just for good evaluate, be sure to reset the ExpiresDefault in your .htaccess file if you're making use of that to help caching.
Anders SandvigAnders Sandvig 21k1616 gold badges6161 silver badges7474 bronze badges 1 one Location a long-in the past Last-Modified has no impact on caching, other than allowing a cached reaction be used longer as a result of heuristic revalidation.
WARNING! This tends to take away: - all stopped containers - all volumes not used by at least 1 container - all networks not used by at least one container - all images without at least one particular container related to them
Right after a certain amount of research we came more info up with the following list of headers that appeared to cover most browsers:
For safety motives we do not want particular pages inside our application to be cached, ever, by the online browser. This have to work for at least the following browsers:
If you have dynamic content which does not gain from ETags, It truly is best to disable it because it incurs small overhead with each request.
There is a big amount of information concerning this situation there but I have nevertheless to find a good reference that describes the benefits of every technique and no matter whether a particular technique has become superseded by a higher level API.
But I also go through that this doesn't work in certain versions of IE. Are there any set of tags that will turn off cache in all browsers?
It stops caching in Firefox and IE, but we haven't tried out other browsers. The following reaction headers are additional by these statements:
are extensions that are considered static data files from IIS instead of despatched into the ASP.Web Runtime. If IIS is ready as many as send out all requests to your ASP.Internet runtime, then Sure, This could apply to all requests, even when the files are static and will be cached.