Re: [whatwg/fetch] Process 103 Early Hints response (PR #1404)

@yutakahirano commented on this pull request.



> +
+       <li><p>If <var>responseStartTime</var> is null, set <var>responseStartTime</var> to
+       <a for=/>coarsened shared current time</a> given <var>fetchParams</var>'s
+       <a for="fetch params">cross-origin isolated capability</a>, immediately after the user
+       agent's HTTP parser receives the first byte of the response (e.g., frame header bytes for
+       HTTP/2 or response status line for HTTP/1.x).
+
+       <li><p>Let <var>status</var> be <a for=response>status</a> of <a for=/>response</a>.
+
+       <li><p>If <var>status</var> is in the range 100 to 199, inclusive:
+        <ol>
+         <li><p>If <var>status</var> is 101, <a for=iteration>break</a>.
+
+         <li><p>If <var>status</var> is 103, then:
+          <ol>
+           <li><p>If <var>fetchParams</var>'s <a for="fetch params">process early hints response</a>

For CORS requests, we shouldn't give any information to clients before checking CORS. 103 response handling happens before checking CORS so we need to make sure that the request is not CORS eligible.

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

Message ID: <whatwg/fetch/pull/1404/review/898669735@github.com>