Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
Revision 6942d58e2a78eccfc404f444acc06b580c66fd79 authored by Geoffrey Sneddon on 16 March 2018, 16:44:36 UTC, committed by Geoffrey Sneddon on 16 March 2018, 16:44:36 UTC 
Make host_ip always exist in the normalised config
1 parent 89ba944
Raw File
Tip revision: 6942d58e2a78eccfc404f444acc06b580c66fd79 authored by Geoffrey Sneddon on 16 March 2018, 16:44:36 UTC
Make host_ip always exist in the normalised config
Tip revision: 6942d58
stub-4.6.1-cache-lifetimes.html 
<!DOCTYPE html>
<html>
<title>Service Workers: Understanding Cache Lifetimes</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#cache-lifetimes">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

The `[Cache][1]` instances are not part of the browser's HTTP cache. The
`[Cache][1]` objects are exactly what authors have to manage themselves. The
`[Cache][1]` objects do not get updated unless authors explicitly request them
to be. The `[Cache][1]` objects do not expire unless authors delete the
entries. The `[Cache][1]` objects do not disappear just because the Service
Worker script is updated. That is, caches are not updated automatically.
Updates must be manually managed. This implies that authors should version
their caches by name and make sure to use the caches only from the version of
the ServiceWorker that can safely operate on.

[1]: #cache-interface

-->



    <script>
        test(function() {
            // not_implemented();
        }, "There are no tests for section Understanding Cache Lifetimes so far.");
    </script>

    </body>
</html>
back to top