summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/service-workers/stub-4.5.2-response.html
diff options
context:
space:
mode:
Diffstat (limited to 'testing/web-platform/tests/service-workers/stub-4.5.2-response.html')
-rw-r--r--testing/web-platform/tests/service-workers/stub-4.5.2-response.html36
1 files changed, 36 insertions, 0 deletions
diff --git a/testing/web-platform/tests/service-workers/stub-4.5.2-response.html b/testing/web-platform/tests/service-workers/stub-4.5.2-response.html
new file mode 100644
index 000000000..fbc72f30a
--- /dev/null
+++ b/testing/web-platform/tests/service-workers/stub-4.5.2-response.html
@@ -0,0 +1,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>
+