Skip to content

Commit

Permalink
Using integrity with "no-cors" is fine same-origin
Browse files Browse the repository at this point in the history
This exception also broke simple service worker passthrough handling.

Tests: see https://bugzilla.mozilla.org/show_bug.cgi?id=1393439.

Fixes whatwg#583.
  • Loading branch information
annevk authored Sep 1, 2017
1 parent a4290d1 commit 686a1ad
Showing 1 changed file with 0 additions and 3 deletions.
3 changes: 0 additions & 3 deletions fetch.bs
Original file line number Diff line number Diff line change
Expand Up @@ -4959,9 +4959,6 @@ constructor must run these steps:
<li><p>If <var>r</var>'s <a for=Request>request</a>'s <a for=request>method</a> is not a
<a>CORS-safelisted method</a>, then <a>throw</a> a <code>TypeError</code>.

<li><p>If <var>request</var>'s <a for=request>integrity metadata</a> is not the empty string,
then <a>throw</a> a <code>TypeError</code>.

<li><p>Set <var>r</var>'s <a for=Request>headers</a>'s <a for=Headers>guard</a> to
"<code>request-no-cors</code>".
</ol>
Expand Down

0 comments on commit 686a1ad

Please sign in to comment.