- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 06 Apr 2022 02:04:18 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 6 April 2022 09:04:30 UTC
@annevk 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. Can't we check if request's client is a secure context? (With that referencing the definition in HTML.) That should account for `localhost` as well as nested contexts and such. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1406#discussion_r843691564 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1406/review/933133396@github.com>
Received on Wednesday, 6 April 2022 09:04:30 UTC