Cache.put()
Experimental: 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()
(en-US) one or more requests, then add the result straight to your cache. In such cases you are better off using Cache.add()
(en-US)/Cache.addAll()
(en-US), 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);
})
참고: put()
will overwrite any key/value pair previously stored in the cache that matches the request.
참고: Cache.add
(en-US)/Cache.addAll
(en-US) 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
(en-US)/Cache.addAll
(en-US) can't be used to store opaque responses, whereas Cache.put
can.
참고: Initial Cache implementations (in both Blink and Gecko) resolve Cache.add
(en-US), Cache.addAll
(en-US), 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.
Syntax
cache.put(request, response).then(function() {
// request/response pair has been added to the cache
});
Parameters
- request
-
The
Request
you want to add to the cache. - response
-
The
Response
(en-US) you want to match up to the request.
Return value
A Promise
that resolves with void.
참고: The promise will reject with a TypeError
if the URL scheme is not http
or https
.
Examples
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:
- Check whether a match for the request is found in the
CacheStorage
(en-US) usingCacheStorage.match()
(en-US). If so, serve that. - If not, open the
v1
cache usingopen()
, put the default network request in the cache usingCache.put()
and return a clone of the default network request usingreturn response.clone()
. Clone is needed becauseput()
consumes the response body. - If this fails (e.g., because the network is down), return a fallback response.
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 |
---|
Service Workers # cache-put |
브라우저 호환성
BCD tables only load in the browser