| OLD | NEW |
|---|
| (Empty) | |
| 1 <!DOCTYPE html> |
| 2 <html> |
| 3 <title>Service Workers: Response</title> |
| 4 <head> |
| 5 <link rel="help" href="https://w3c.github.io/ServiceWorker/#response"> |
| 6 <script src="/resources/testharness.js"></script> |
| 7 <script src="/resources/testharnessreport.js"></script> |
| 8 |
| 9 </head> |
| 10 <body> |
| 11 |
| 12 <!-- |
| 13 |
| 14 `Response` objects are mutable and constructable. They model HTTP responses. |
| 15 The `fetch()` API returns this type for same-origin responses. |
| 16 |
| 17 It may be possible to set the `Location` header of a `Response` object to |
| 18 someplace not in the current origin but this is not a security issue. |
| 19 Cross-origin response bodies are opaque to script, and since only same-origin |
| 20 documents will encounter these responses, the only systems the Service Worker |
| 21 can "lie to" are same-origin (and therefore safe from the perspective of other |
| 22 origins). |
| 23 |
| 24 --> |
| 25 |
| 26 |
| 27 |
| 28 <script> |
| 29 test(function() { |
| 30 // not_implemented(); |
| 31 }, "There are no tests for section Response so far."); |
| 32 </script> |
| 33 |
| 34 </body> |
| 35 </html> |
| 36 |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2415873002:
Import w3c tests for the service workers (Closed)
