Re: [whatwg/fetch] Use internal response for Server-Timing (PR #1584)

@annevk commented on this pull request.



> @@ -4621,7 +4621,11 @@ steps:
   <a for="fetch params">request</a>'s <a for=request>client</a> is a <a>secure context</a>, then set
   <var>timingInfo</var>'s <a for="fetch timing info">server-timing headers</a> to the
   result of <a for="header list">getting, decoding, and splitting</a> `<code>Server-Timing</code>`
-  from <var>response</var>'s <a for=response>header list</a>.
+  from <var>response</var>'s <a for="filtered response">internal response</a>'s
+  <a for=response>header list</a>.

Step 14.2 of main fetch seems to ensure there's either a network error or a filtered response so I think we're good.

HTML defines "unsafe response" which we should maybe define here as well, but would be good to know where it's needed first.

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

Message ID: <whatwg/fetch/pull/1584/review/1234212143@github.com>