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-4.5.2-response.html 
<!DOCTYPE html>
<html>
<title>Service Workers: Response</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#response">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`Response` objects are mutable and constructable. They model HTTP responses.
The `fetch()` API returns this type for same-origin responses.

It may be possible to set the `Location` header of a `Response` object to
someplace not in the current origin but this is not a security issue.
Cross-origin response bodies are opaque to script, and since only same-origin
documents will encounter these responses, the only systems the Service Worker
can "lie to" are same-origin (and therefore safe from the perspective of other
origins).

-->



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

    </body>
</html>
back to top