From eefc88208f0b1a112d553d3cd9d8a0512c49095a Mon Sep 17 00:00:00 2001
From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 28 May 2018 14:39:53 +0200
Subject: [PATCH] Make CORS-preflight fetches set the CORS flag

Otherwise a 401 response would not necessarily result in rejection.

Fixes #741.
---
 fetch.bs | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/fetch.bs b/fetch.bs
index 5598cb1d5..0a2ec88e9 100644
--- a/fetch.bs
+++ b/fetch.bs
@@ -4138,8 +4138,8 @@ the <a>CORS protocol</a> is understood. The so-called <a>CORS-preflight request<
 successful it populates the <a>CORS-preflight cache</a> to minimize the
 number of these <a lt="CORS-preflight fetch">fetches</a>.
 
-<p>To perform a <dfn id=cors-preflight-fetch-0>CORS-preflight fetch</dfn> using <var>request</var>, run these
-steps:
+<p>To perform a <dfn id=cors-preflight-fetch-0>CORS-preflight fetch</dfn> using <var>request</var>,
+run these steps:
 
 <ol>
  <li>
@@ -4184,8 +4184,7 @@ steps:
   0x2C is not the way this was implemented, for better or worse.
 
  <li><p>Let <var>response</var> be the result of performing an
- <a>HTTP-network-or-cache fetch</a> using
- <var>preflight</var>.
+ <a>HTTP-network-or-cache fetch</a> using <var>preflight</var> with the <i>CORS flag</i> set.
 
  <li>
   <p>If a <a for=cors>CORS check</a> for <var>request</var> and <var>response</var> returns success