commit 7d97c3a8550e35ce8af356fa6e3e8a0553a61140
author Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Thu Sep 21 10:44:54 2017
committer Commit Bot <commit-bot@chromium.org> Thu Sep 21 10:44:54 2017
tree 79d42bf53b584b225e840b209cefc466ddbb338a
parent b11586a5055db9515844239c82c7a9ca6d0bb6c8

Fetch: Do not check |integrity| in no-cors mode when constructing a Request

Adapt to https://github.com/whatwg/fetch/pull/584, which removed the check
for |integrity|'s value when constructing a Request in no-cors mode.

Per https://github.com/whatwg/fetch/issues/583: "the issue is that it's
pretty common to do <script integrity="hash"> in your document. This creates
a no-cors request by default. If their service worker script passes through
with fetch(evt.request) then they will get a TypeError."

Note that the external tests added in
https://github.com/w3c/web-platform-tests/commit/96adf8a1a0cdeb70280f0a0e1ef840602c0ce8b0
are still flaky.

Bug: 766975, 766983
Change-Id: I1a787ee39ed94db49ba18f8675edc7dc3019ed26
Reviewed-on: https://chromium-review.googlesource.com/674694
Commit-Queue: Raphael Kubo da Costa (rakuco) <raphael.kubo.da.costa@intel.com>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#503412}