Re: [whatwg/fetch] Clarify cors requests need cors response tainting (#1170)

@sideshowbarker commented on this pull request.



> @@ -1390,7 +1390,8 @@ to not have to set <a for=/>request</a>'s <a for=request>referrer</a>.
   <a>network error</a> if the request is not made to a same-origin URL.
 
   <dt>"<code>cors</code>"
-  <dd>Makes the request a <a>CORS request</a>. Fetch will return a <a>network error</a> if the
+  <dd>For requests whose <a for=request>response tainting</a> is also "<code>cors</code>", makes the

> "gets set to" seems more accurate since response tainting is not set by those creating the request.

Made it so

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1170#discussion_r577484235

Received on Wednesday, 17 February 2021 10:11:54 UTC