The updateViaCache
read-only property of the ServiceWorkerRegistration
interface updates the cache using the mode specified in the call to ServiceWorkerContainer.register
. Requests for importScripts
still go via the HTTP cache. updateViaCache
offers control over this behavior.
On this page
ServiceWorkerRegistration: updateViaCache property
Value
Returns one of the following values:
imports
, meaning the HTTP cache is not consulted for update of the service worker, but is consulted forimportScripts
.all
, meaning the HTTP cache is consulted in both casesnone
, meaning the HTTP cache is never consulted.
Examples
The following example shows the use of updateViaCache.
js
if ("serviceWorker" in navigator) {
navigator.serviceWorker
.register("/service-worker.js", {
updateViaCache: "none",
})
.then((registration) => {
registration.addEventListener("updatefound", () => {
// If updatefound is fired, it means that there's
// a new service worker being installed.
console.log(`Value of updateViaCache: ${registration.updateViaCache}`);
});
})
.catch((error) => {
console.error(`Service worker registration failed: ${error}`);
});
}
Specifications
Browser compatibility
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
updateViaCache |
68 | 18 | 57 | No | 55 | 11.1 | 68 | 68 | 57 | 48 | 11.3 | 10.0 |
See also
© 2005–2023 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerRegistration/updateViaCache