Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
Revision 9f72b689165309d4b959f3dbc724f18fe9a77111 authored by Mike West on 05 April 2018, 12:29:12 UTC, committed by Chromium WPT Sync on 05 April 2018, 12:29:12 UTC 
Add a runtime flag to restrict AppCache to secure contexts.
 
This patch adjusts the `SecureContext` IDL attribute to take an argument,
as we need to restrict the relevant bits and pieces to secure contexts
iff a specific flag is set. We'll unfortunately need to keep that in place
until and unless we decide that we can reasonably remove an enterprise
opt-out.

Intent to Deprecate/Remove: https://groups.google.com/a/chromium.org/d/msg/blink-dev/ANnafFBhReY/1Xdr53KxBAAJ
Spec bug: https://github.com/whatwg/html/issues/3440

Bug: 588931
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I5bedd2ca6f420a88ddbcff65e4223fad224ac0a7
Reviewed-on: https://chromium-review.googlesource.com/982625
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548391}
1 parent d725f2a
Raw File
Tip revision: 9f72b689165309d4b959f3dbc724f18fe9a77111 authored by Mike West on 05 April 2018, 12:29:12 UTC
Add a runtime flag to restrict AppCache to secure contexts.
Tip revision: 9f72b68
stub-4.5.4-opaque-response.html 
<!DOCTYPE html>
<html>
<title>Service Workers: OpaqueResponse</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#opaque-response">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`OpaqueResponse` objects are immutable but constructable. The `fetch()` API
returns this type for cross-origin responses.

Their role is to encapsulate the security properties of the web platform. As
such, their `body` attribute will always be `undefined` and the list of
readable `headers` is heavily filtered.

`OpaqueResponse` objects may be forwarded on to rendering documents in exactly
the same way as mutable `Response` objects.

-->



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

    </body>
</html>
back to top