Service Worker is also Being cached in Chrome?

Question

I built a Progressive Web App, https://www.tavest.com. I don't understand why my service worker is also being cached in Chrome? https://www.tavest.com/service-worker-tavest.js So when I change the service-worker, the chrome doesn't detect the change thus the service worker is not updating.

Eventough I refresh the page many times, it's still the same. However, in Mozilla it works just fine. Here's my code for installing the service worker

if ('serviceWorker' in navigator && (window.location.protocol === 'https:')) {
      navigator.serviceWorker.register('/service-worker-tavest.js')
      .then(function(registration) {
        // updatefound is fired if service-worker.js changes.
        registration.onupdatefound = function() {
          // updatefound is also fired the very first time the SW is installed,
          // and there's no need to prompt for a reload at that point.
          // So check here to see if the page is already controlled,
          // i.e. whether there's an existing service worker.
          if (navigator.serviceWorker.controller) {
            // The updatefound event implies that registration.installing is set:
            // https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#service-worker-container-updatefound-event
            var installingWorker = registration.installing;

            installingWorker.onstatechange = function() {
              switch (installingWorker.state) {
                case 'installed':
                  // At this point, the old content will have been purged and the
                  // fresh content will have been added to the cache.
                  // It's the perfect time to display a "New content is
                  // available; please refresh." message in the page's interface.
                  console.warn('New content is available, please refresh the page');
                  
                  break;

                case 'redundant':
                  throw new Error('The installing ' +
                                  'service worker became redundant.');

                default:
                  // Ignore
              }
            };
          }
        };
      }).catch(function(e) {
        console.error('Error during service worker registration:', e);
      });
    }

Thank you for your help

Warm regards,

Possible duplicate of [Service worker JavaScript update frequency (every 24 hours?)](http://stackoverflow.com/questions/38843970/service-worker-javascript-update-frequency-every-24-hours) — Jeff Posnick, Feb 06 '17 at 15:30

Tony Dinh · Answer 1 · 2019-08-29T03:25:30.387

It's because the service worker is just a normal JS file and it will be browser-cached.

You can set no-cache header to the /service-worker-tavest.js so that the browser will stop caching your service worker file. That way you can have your service worker updated immediately when the new file is uploaded.

Here is how to do that in Nginx:

location /service-worker-tavest.js {
  # Don't use browser cache for service worker file
  add_header cache-control "no-store, no-cache, must-revalidate";
}

score 2 · Answer 2 · answered Mar 01 '17 at 04:24

I think I know the answer regarding to this caching. It is because of "Service worker Lifecycle" in Chrome.

https://www.youtube.com/watch?v=TF4AB75PyIc

Conclusion: The cache in chrome browser is okay because chrome will update the service worker by itself.

Service Worker is also Being cached in Chrome?

2 Answers2