Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)

@noamr commented on this pull request.



> +  <p>Otherwise, if <var>response</var>'s <a for=response>URL</a>'s <a for=url>scheme</a> is
+  "<code>https</code>", then set <var>response</var>'s <a for=response>timing info</a>'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>.
+
+  <p>The user agent may decides to expose `<code>Server-Timing</code>` headers to
+  "<code>http</code>" requests as well.

I don't think localhost being treated as a secure context is defined anywhere in fetch...

I can probably hand-wave something in the note like 

The user agent may decides to expose `<code>Server-Timing</code>` headers to some or all "<code>http</code>" requests as well, e.g. when the <var>response</var>'s <a for=response>URL</a>'s <a for=url>host</a>'s <a for=host>public suffix</a> is "<code>localhost</code>".

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

Message ID: <whatwg/fetch/pull/1406/review/913123791@github.com>