From 334d67a74f93f33e8df941d748f7582da1c58950 Mon Sep 17 00:00:00 2001
From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 24 Aug 2017 16:48:59 +0200
Subject: [PATCH] Using integrity with "no-cors" is fine same-origin

This exception also broke simple service worker passthrough handling.

Tests: ...

Fixes #583.
---
 fetch.bs | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/fetch.bs b/fetch.bs
index 839376071..1728f89ce 100644
--- a/fetch.bs
+++ b/fetch.bs
@@ -4979,9 +4979,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>