Skip to content

Commit 9334fcb

Browse files
committed
Make CORS-preflight fetches set the CORS flag
Otherwise a 401 response would not necessarily result in rejection. Fixes #741.
1 parent fa6f2b0 commit 9334fcb

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

fetch.bs

+3-4
Original file line numberDiff line numberDiff line change
@@ -4144,8 +4144,8 @@ the <a>CORS protocol</a> is understood. The so-called <a>CORS-preflight request<
41444144
successful it populates the <a>CORS-preflight cache</a> to minimize the
41454145
number of these <a lt="CORS-preflight fetch">fetches</a>.
41464146

4147-
<p>To perform a <dfn id=cors-preflight-fetch-0>CORS-preflight fetch</dfn> using <var>request</var>, run these
4148-
steps:
4147+
<p>To perform a <dfn id=cors-preflight-fetch-0>CORS-preflight fetch</dfn> using <var>request</var>,
4148+
run these steps:
41494149

41504150
<ol>
41514151
<li>
@@ -4190,8 +4190,7 @@ steps:
41904190
0x2C is not the way this was implemented, for better or worse.
41914191

41924192
<li><p>Let <var>response</var> be the result of performing an
4193-
<a>HTTP-network-or-cache fetch</a> using
4194-
<var>preflight</var>.
4193+
<a>HTTP-network-or-cache fetch</a> using <var>preflight</var> with the <i>CORS flag</i> set.
41954194

41964195
<li>
41974196
<p>If a <a for=cors>CORS check</a> for <var>request</var> and <var>response</var> returns success

0 commit comments

Comments
 (0)