Skip to main content

Browse the archive

Revision 4f06a45252465792447f80b6559b17c4c4e9712c authored by Daniel Vogelheim on 10 April 2018, 13:07:39 UTC, committed by Chromium WPT Sync on 10 April 2018, 13:07:39 UTC 
Implement deprecation of content type sniffing for workers.
 
Allow control of the deprecation via runtime enabled features, with a first
step for logging a warning to the console, and the second step to block it
outright.

Intent:  https://groups.google.com/a/chromium.org/d/msg/blink-dev/35t5cJQ3J_Q/FH45dl0vAwAJ

Change-Id: I1be1001cbbef152458119b1516750bb4f1d1e4de
Reviewed-on: https://chromium-review.googlesource.com/975611
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549495}
1 parent 069680c
Raw File
header-user-agent-sync.htm 
<!DOCTYPE html>
<html>
<head>
    <title>Test that sync requests (both OPTIONS preflight and regular) are sent with the User-Agent header</title>
    <script src="/resources/testharness.js"></script>
    <script src="/resources/testharnessreport.js"></script>
    <script src="/common/get-host-info.sub.js"></script>
</head>
<body>
<script type="text/javascript">
  test(function() {
    let xhr = new XMLHttpRequest;
    xhr.open("post", get_host_info().HTTP_REMOTE_ORIGIN + "/xhr/resources/header-user-agent.py", false);
    xhr.setRequestHeader("x-test", "foobar");
    xhr.send();
    assert_equals(xhr.responseText, "PASS");
  }, "Sync request has User-Agent header");
</script>
</body>
</html>
back to top