This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The put()
method of the Cache
interface allows key/value pairs to be added to the current Cache
object.
Often, you will just want to fetch()
one or more requests, then add the result straight to your cache. In such cases you are better off using Cache.add()
/Cache.addAll()
, as they are shorthand functions for one or more of these operations.
fetch(url).then(function(response) { if (!response.ok) { throw new TypeError('Bad response status'); } return cache.put(url, response); })
Note: put()
will overwrite any key/value pair previously stored in the cache that matches the request.
Note: Cache.add
/Cache.addAll
do not cache responses with Response.status
values that are not in the 200 range, whereas Cache.put
lets you store any request/response pair. As a result, Cache.add
/Cache.addAll
can't be used to store opaque responses, whereas Cache.put
can.
Note: Initial Cache implementations (in both Blink and Gecko) resolve Cache.add
, Cache.addAll
, and Cache.put
promises when the response body is fully written to the disk. More recent spec versions state that the browser can resolve the promise as soon as the entry is recorded in the database even if the response body is still streaming in.
cache.put(request, response).then(function() { // request/response pair has been added to the cache });
Request
you want to add to the cache.Response
you want to match up to the request.A Promise
that resolves with void.
Note: The promise will reject with a TypeError
if the URL scheme is not http
or https
.
This example is from the MDN sw-test example (see sw-test running live). Here we wait for a FetchEvent
to fire. We construct a custom response like so:
CacheStorage
using CacheStorage.match()
. If so, serve that.v1
cache using open()
, put the default network request in the cache using Cache.put()
and return a clone of the default network request using return response.clone()
. Clone is needed because put()
consumes the response body.var response; var cachedResponse = caches.match(event.request).catch(function() { return fetch(event.request); }).then(function(r) { response = r; caches.open('v1').then(function(cache) { cache.put(event.request, response); }); return response.clone(); }).catch(function() { return caches.match('/sw-test/gallery/myLittleVader.jpg'); });
Specification | Status | Comment |
---|---|---|
Service Workers The definition of 'Cache' in that specification. | Editor's Draft | Initial definition. |
Feature | Chrome | Edge | Firefox (Gecko) | Internet Explorer | Opera | Safari (WebKit) |
---|---|---|---|---|---|---|
Basic support | 40 | (Yes) | 39 (39)[1] | No support | 27 | No support |
Require HTTPS | 46 | (Yes) | (Yes)[1] | ? | 33 | ? |
Feature | Android Webview | Chrome for Android | Firefox Mobile (Gecko) | Firefox OS | IE Mobile | Opera Mobile | Safari Mobile |
---|---|---|---|---|---|---|---|
Basic support | 40 | 40 | 39.0 (39) | ? | No support | 27 | No support |
Require HTTPS | 46 | 46 | (Yes) | ? | ? | 33 | ? |
[1] Service workers (and Push) have been disabled in the Firefox 45 & 52 Extended Support Releases (ESR.)
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/Cache/put