#FIREFOX REFRESH PAGE CACHE HOW TO#
#FIREFOX REFRESH PAGE CACHE UPDATE#
#FIREFOX REFRESH PAGE CACHE CODE#

The truth is that I'm desperate because when I give something that I think works, when I check it with my boss he does not refresh it :-(, and the bad thing is that as I say I do not know how to really check that really, every time I enter the web, the latest version is requested from the server. I have also tried, put in the templateUrl: './? v1'Īs I have seen in some answers, but neither. I tried to include in the request header, Cache-Control: no-cache, as you can see in the image, but that does not work for me. The first thing is that I have very difficult to test if the solution works because when I upload a new version, sometimes I see it without having to do more than refresh the page, and other times I need to open the console and force the refresh emptying cache. I would like to avoid the browser cache and I am trying several alternatives but none of them work.

#FIREFOX REFRESH PAGE CACHE UPDATE#

So if you don't have a specific reason for using them consider turning them off.I have a problem with an Angular application that I update very often. Other servers will ignore the header if they don't support it.Įtags also don't work with byte-range requests.

#FIREFOX REFRESH PAGE CACHE CODE#

Without looking at the code in Firefox caching heuristics I can't say for sure but it should be easy to test. The possible workaround for Firefox is adding the Cache-Control Immutable options. This can be handled on your server or if you can't control it by rewrite rules on your CDN. That is done by including W/ in front of the ETags value, i.e.

You can modify the revalidation behavior by making it a weak ETag. If it has not changed, the server/proxy returns a 304. The If-None-Match header tells the server what version or versions it has. When an Etag is present, the client or intermediary caches need to perform a GET or HEAD ensuring the content being served hasn't changed. Technically, Firefox is handling it correctly. Just to be more verbose let me elaborate on ETags. (Note that, according to MDN, Firefox only respects immutable on https content, so this still wouldn't work on your http test page above.) If this refresh behavior is an important use case for your application (as opposed to just something you're using for debugging purposes) adding Cache-Control: immutable should solve this problem in Firefox.

(See this answer for more on this distinction). Chrome's approach is to make its refresh behavior smarter and more sophisticated, while Firefox has chosen to rely on the developer explicitly indicating that a non-stale resource never needs revalidation by using the Cache-Control: immutable response header. Now, with the advent of sites showing real-time content, the use of 'refresh' may be quite different.Ĭhrome and Firefox seem to be taking different paths to deal with this. It was probably reasonable at one time to assume that if a user was actively refreshing their page it was because something went wrong and they needed to start from scratch.

Put simply: Firefox revalidates cached content on browser refresh. A plain refresh, though, not shift- or shift-command-, but just a plain refresh. I've discovered that this only happens on a page refresh. I've tried with devtools closed too, and I keep seeing the 304s in my server logs. I've ensured that caching is enabled in devtools. I've experimented with various cache-related headers and read the standard on what's 'cacheable'. I can't figure why Firefox ignores the cache headers and keeps going to the server for the 304. Here is an example of on such request that results in a 304: As you can see, I include cache-control: public, max-age, expires, etag and last-modified and the resource is served from 'memory cache':įirefox, however, does not respect these headers and re-validates the resources on every load! My server is hit with a request for each profile pic every time the page loads, and returns a 304: Here's an example of one of these resources in Chrome. Chrome seems to respect my response headers, and does not re-validate the resources: I have some image resources that are immutable and can be cached forever.

Firefox refresh page cache