File: stub-4.5.2-response.html

package info (click to toggle)
firefox-esr 52.8.1esr-1~deb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 1,983,244 kB
  • sloc: cpp: 4,810,275; ansic: 2,004,548; python: 451,282; java: 241,615; asm: 178,649; xml: 136,302; sh: 82,207; makefile: 22,575; perl: 15,783; objc: 4,389; yacc: 1,816; ada: 1,697; pascal: 1,519; lex: 1,257; cs: 879; exp: 499; php: 436; lisp: 258; awk: 152; sed: 51; ruby: 47; csh: 27
file content (36 lines) | stat: -rw-r--r-- 1,017 bytes parent folder | download | duplicates (8) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
 
<!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>