Skip to main content

Browse the archive

Revision 6668ff3716086d3f8efead0f5db2d8d2864c3563 authored by Robert Ma on 21 March 2018, 17:35:46 UTC, committed by Robert Ma on 21 March 2018, 17:35:46 UTC 
Fix resources/test (when running locally)
 
1. Check the HTTP port of wptserve instead of HTTPS to avoid the
   unnecessary complexities of setting up SSL context (which may fail in
   some environments).
2. Use exponential backoff when waiting for wptserve and specify a
   maximum retry to avoid indefinite hang.
3. Use `terminate` instead of `kill` to give wptserve a chance to clean
   up, which is especially useful when running locally.
1 parent dbb38a6
Raw File
stub-5.1-origin-relativity.html 
<!DOCTYPE html>
<html>
<title>Service Workers: Origin Relativity</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#origin-relativity">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

One of the advanced concerns that major applications would encounter is whether
they can be hosted from a CDN. By definition, these are servers in other
places, often on other domains. Therefore, Service Workers cannot be hosted on
CDNs. But they can include resources via [importScripts()][1]. The reason for
this restriction is that Service Workers create the opportunity for a bad actor
to turn a bad day into a bad eternity.

[1]: http://goo.gl/Owcfs2

-->



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

    </body>
</html>
back to top